summaryrefslogtreecommitdiff
path: root/gitdb
Commit message (Collapse)AuthorAgeFilesLines
* chore(rename): gitdb2 v2.02.0.0Sebastian Thiel2016-10-162-1/+1
| | | | v2 is chosen to better match the name.
* support optional gitdb_speedupsThomas Grainger2016-10-046-1270/+3
|
* Merge pull request #28 from scop/withSebastian Thiel2016-07-304-15/+10
|\ | | | | Handle more file open/close with "with"
| * Handle more file open/close with "with"Ville Skyttä2016-07-274-15/+10
| |
* | Spelling fixesVille Skyttä2016-07-279-10/+10
|/
* fix(loose): avoid unnecessary file rename on windowsSebastian Thiel2015-10-042-4/+9
| | | | | | This should workaround possible permission issues. Related to https://github.com/gitpython-developers/GitPython/issues/353
* docs(gitdb): discourage usage of GitDB typeSebastian Thiel2015-08-221-1/+5
|
* Duplicate `const` fixedGermán M. Bravo2015-04-071-5/+5
| | | | Remove duplicate `const` to stop the warning: "duplicate 'const' declaration specifier"
* Bumped version to 0.6.40.6.4Sebastian Thiel2015-01-121-1/+1
|
* Adjusted stream logic to make it work on all tested platforms ... .Sebastian Thiel2015-01-123-4/+11
| | | | | | | | | | | | | | | | | As taken from https://github.com/gitpython-developers/gitdb/blob/master/gitdb/stream.py#L292 -> NOTE: Behavior changed in PY2.7 onward, which requires special handling to make the tests work properly. They are thorough, and I assume it is truly working. Why is this logic as convoluted as it is ? Please look at the table in https://github.com/gitpython-developers/gitdb/issues/19 to learn about the test-results. Bascially, on py2.6, you want to use branch 1, whereas on all other python version, the second branch will be the one that works. However, the zlib VERSIONs as well as the platform check is used to further match the entries in the table in the github issue. This is it ... it was the only way I could make this work everywhere. IT's CERTAINLY GOING TO BITE US IN THE FUTURE ... . <- Fixes #19
* minor spell fixes + empty line unification + comparison for python 2.6Yaroslav Halchenko2015-01-084-9/+7
|
* Make tests independent of actual repository dataSebastian Thiel2015-01-082-4/+5
| | | | | | | Therefore, hardcoded sha's are not allowed anymore, as the contents of the repository is unknown. Fixes #16, for real this time ;)
* Removed unused imports - should have been in the last commit obviouslySebastian Thiel2015-01-082-2/+0
|
* Fixed up tests to use the GITDB_TEST_GIT_REPO_BASE at all timesSebastian Thiel2015-01-086-41/+43
| | | | | | | I have verified that all tests are working, even without a parent git repository, as long as the said environment variable is set. Fixes #16
* Protected stream closure against possibilty of being a bytesSebastian Thiel2015-01-072-2/+4
| | | | | | For some reason, it gets bytes where it did expect a stream ... . Probably I should have figured out where this was input, instead of fixing it the brutal way
* Fixed possible file-handle leakSebastian Thiel2015-01-071-3/+11
| | | | | Configured travis to artificially restrict handle count to protect from regression in that regard
* Bumped version to 0.6.30.6.3Sebastian Thiel2015-01-061-1/+1
|
* Fixed yet another issue with smmap's latest changesSebastian Thiel2015-01-062-2/+15
| | | | Now we deal with memory views as well ...
* Fixed python 3 compatibility issue that only showed on windows0.6.2Sebastian Thiel2015-01-062-7/+7
| | | | And bumped version to 0.6.2
* A minor fix after porting git-python over to PY3Sebastian Thiel2015-01-061-1/+1
| | | | It doesn't do anything (in terms of fixing an issue), but it should be more correct than what was there previously
* Applied autopep8Sebastian Thiel2015-01-0434-283/+366
| | | | autopep8 -v -j 8 --max-line-length 120 --in-place --recursive
* Improved decompression test to scan the entire git repository, instead of ↵Sebastian Thiel2015-01-011-2/+4
| | | | | | | | just packs This should make it easier to assert the issue is truly fixed now [skip ci]
* Bumped new versionSebastian Thiel2015-01-012-3/+3
| | | | Fixed tiny issue in python 3
* Added integrity test for loose objects to search large datasets forSebastian Thiel2015-01-011-0/+31
| | | | | | the issue described in https://github.com/gitpython-developers/GitPython/issues/220 See test notes for proper usage, it all depends on a useful dataset with high entropy
* Slightly improved loose object decompression testSebastian Thiel2015-01-011-1/+9
|
* Increased initial size of decompressed data to obtain loose object header ↵Sebastian Thiel2015-01-014-8/+15
| | | | | | | | | information This appears to fix https://github.com/gitpython-developers/GitPython/issues/220 , in this particular case. Nonetheless, we might just have gotten lucky here, and the actual issue is not yet solved and can thus re-occour. It would certainly be best to churn through plenty of loose objects to assure this truly works now. Maybe the pack could be recompressed as loose objects to get a sufficiently large data set
* Added readthedocs badgeSebastian Thiel2014-11-191-0/+0
|
* It seems zlib works differently in py26, and thus requires special handling.py2n3Sebastian Thiel2014-11-142-17/+11
| | | | This also explains why the tests suddenly stopped working - after all, the interpreter changed ... .
* Now I am skipping a problematic test on travis CI.Sebastian Thiel2014-11-141-2/+12
| | | | Maybe I can find a py 2.6 interpreter somewhere to reproduce it.
* Added requirements.txt for pip, and optimized test-suite performance on travis.Sebastian Thiel2014-11-146-4/+31
| | | | With a bit of luck, this one will just work now.
* Fixed incorrect computation of compressed bytes read in zlib decompression ↵Sebastian Thiel2014-11-141-1/+4
| | | | stream.
* Performance tests are now part of the test-suite.Sebastian Thiel2014-11-145-46/+43
| | | | | | | By default, a small repository will be tested, which doesn't take that long actually (~20s) Additionally, that way we enforce correctness tests, which didn't run by default previously. As we are handling data here, we must be sure that it's handled correctly, thus the tests should run.
* setup.py works now, and binary python module can now be loaded as well.Sebastian Thiel2014-11-132-3/+0
|
* reduced usage of force_bytes as clients are expected to pass bytes.Sebastian Thiel2014-11-134-17/+10
| | | | | | It was useful for debugging though, maybe an explicit type assertions would help others ? As 'others' will be gitpython, I suppose I can handle it myself
* Now tests work consistently in py2 and 3Sebastian Thiel2014-11-139-110/+178
| | | | It's a nice way of saying that there is still one failing, consistently.
* Fully removed all async dependenciesSebastian Thiel2014-11-1312-287/+4
|
* Fixed all applicable lint issuesSebastian Thiel2014-11-1326-81/+75
|
* Merge branch 'kevin-brown-issue_4' into py2n3Sebastian Thiel2014-11-1332-1360/+1478
|\ | | | | | | | | | | | | | | | | | | Conflicts: gitdb/base.py gitdb/fun.py gitdb/pack.py gitdb/stream.py gitdb/test/lib.py gitdb/util.py
| * Made sure xrange is used instead of range in python 2Sebastian Thiel2014-11-139-29/+20
| | | | | | | | | | | | | | range in py2 will return a list, which can mean a lot of time and memory is spent on generating it even though it's just used for iteration. Simplified implementation of MAXSIZE
| * Convert types to bytesKevin Brown2014-07-213-22/+26
| | | | | | | | | | This makes it easier to deal with things internally as now everything is passed as bytes.
| * Fixed a few more encoding issuesKevin Brown2014-07-163-3/+8
| | | | | | | | | | | | | | | | Bytes should always be returned from the streams, so the tests should be checking against byte strings instead of text strings. This also fixes the `sha_iter` as it relied on the Python 2 `iterkeys` which has been renamed to `keys` in Python 3.
| * Start up compat and encoding filesKevin Brown2014-07-1612-44/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were a few things which were being reused consistently for compatibility purposes, such as the `buffer`/`memoryview` functions as well as the `izip` method which needed to be aliased for Python 3. The `buffer` function was taken from `smmap` [1] and reworked slightly to handle the optional third parameter. This also adds a compatibility file dedicated entirely to encoding issues, which seem to be the biggest problem. The main functions were taken in part from the Django project [2] and rewritten slightly because our needs are a bit more narrow. A constants file has been added to consistently handle the constants which are required for the gitdb project in the core and the tests. This is part of a greater plan to reorganize the `util.py` file included in this project. This points the async extension back at the original repository and points it to the latest commit. [1]: https://github.com/Byron/smmap/blob/1af4b42a2354acbb53c7956d647655922658fd80/smmap/util.py#L20-L26 [2]: https://github.com/django/django/blob/b8d255071ead897cf68120cd2fae7c91326ca2cc/django/utils/encoding.py
| * Fix Python 2 failuresKevin Brown2014-07-135-13/+14
| |
| * Making a bit of progress...Kevin Brown2014-07-138-62/+20
| | | | | | | | | | | | | | This changes the internals to use BytesIO over StringIO, which fixed a few of the failing tests in Python 3. We are only importing from `io` now, instead of the entire chain, as this is available in Python 2.6+.
| * Can't compare memoryview instances, convert to bytesKevin Brown2014-07-131-1/+2
| |
| * Bytes for everyone!Kevin Brown2014-07-134-9/+8
| |
| * More bytes handlingKevin Brown2014-07-135-5/+19
| |
| * Better handling of bytesKevin Brown2014-07-133-18/+33
| | | | | | | | | | | | | | This adds a `byte_ord` version of `ord` which will let `bytes` safely pass through in Python 3. `cmp` was also swapped out as it has been dropped in Python 3.
| * Use memoryview instead of bufferKevin Brown2014-07-131-1/+4
| | | | | | | | | | | | | | This uses memoryview by default, which is supported in Python 3 and Python 2.7, but not Python 2.6, and falls back to the old `buffer` type in Python 2.6 and when the memoryview does not support the type, such as when mmap instaces are passed in.
| * Convert strings to bytes for PY3Kevin Brown2014-07-134-15/+15
| | | | | | | | | | | | In Python 3, the default string type is now the Python 2 unicode strings. The unicode strings cannot be converted to a byte stream, so we have to convert it before writing to the streams.
View Lorry Controller Status