summaryrefslogtreecommitdiff
path: root/gitdb
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Bump patch level: remove support for old python versions2.0.4Sebastian Thiel2018-10-131-1/+1
| |/
* | Fix for UnicodeEncodeError in git.Repo.clone_from() when path contains ↵xarx002019-04-051-1/+1
|/ | | | non-ascii characters
* Upgrade Python syntax with pyupgrade https://github.com/asottile/pyupgradeHugo2018-09-073-3/+3
|
* Drop support for EOL PythonHugo2018-09-071-4/+1
|
* Upgrade makefile2.0.3Sebastian Thiel2017-09-282-1/+1
|
* change codecs to open with support encoding="utf-8"wangweichen2017-07-131-1/+2
|
* fix open encoding error.wangweichen2017-07-131-1/+1
|
* Typosstuertz2017-03-271-3/+3
|
* fixed to be py26 compatstuertz2017-03-271-2/+4
|
* Use range instead of xrange, good enough herestuertz2017-03-271-1/+1
|
* close smmap handles, to be able to delete files / trees in process (req. for ↵stuertz2017-03-272-2/+17
| | | | windows)
* Release the file handle, before deleting, otherwise win fails.stuertz2017-03-261-0/+1
|
* Fixed Tests / Code for Windows.stuertz2017-03-262-6/+25
| | | | | Sometimes the OS or some other process has the handle to file a bit longer, and the file could not be deleted immediatly. Retry 10 Times with 100ms distance.
* Skip Test on Windowsstuertz2017-03-261-0/+9
| | | | | Currently renaming files is not supported while the the OS doesn't support renaming open files. When closing the file, as done in the code by using http://smmap.readthedocs.io/en/latest/api.html#smmap.mman.StaticWindowMapManager.force_map_handle_removal_win force_map_handle_removal_win, we can rename, but the cache does still have a handle to this file and crashes.
* tc: HALF FIX of `test_pack_entity ()`Kostis Anagnostopoulos2016-10-221-3/+6
| | | | | + On Windows, you cannot write onto a file held by another live file-pointer (test_pack.py:#L204). + The TC fails later, on clean up (the usual).
* TCs: fix div-by-zero on elapsed times (appveyor CPU is fast!)Kostis Anagnostopoulos2016-10-223-11/+11
|
* 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
View Lorry Controller Status