delta/python-packages/gitdb.git/gitdb/utils, branch v2.1.1.dev1 github.com: gitpython-developers/gitdb.git fix(leaks): close "leaky" `memoryview` on mmaps after `to_bytes()` 2016-10-28T12:34:30+00:00 Kostis Anagnostopoulos ankostis@gmail.com 2016-10-27T13:10:26+00:00 18bdab2264cf9db354e49f23b3ec1e11ff4d09f4 All 3 gitpython projects stopped using memoryviews, but it's probably safe to release also user's memviews it after it has been converted to bytes. 
All 3 gitpython projects stopped using memoryviews, but it's probably
safe to release also user's memviews it after it has been converted to
bytes.
 fix(compat): PY3-check must hold even for PY4 2016-10-28T12:34:30+00:00 Kostis Anagnostopoulos ankostis@gmail.com 2016-10-25T15:28:03+00:00 a1205fbd3183fca49ea75d25b861d48bd5bb63e6 






fix(io): BREAKING, wrap more out-stream usages
2016-10-27T21:55:16+00:00

Kostis Anagnostopoulos
ankostis@gmail.com

2016-10-25T13:03:00+00:00

6e5e30877899ca0d503ce082eab780956259e191

+ chrore(deps): depend on *contextlib2* for `ExitStack` in PY2.
+ refact(util): BREAKING API move consts out of utils.
+ style(pep8): fixe all sources.





+ chrore(deps): depend on *contextlib2* for `ExitStack` in PY2.
+ refact(util): BREAKING API move consts out of utils.
+ style(pep8): fixe all sources.







Fixed yet another issue with smmap's latest changes
2015-01-06T17:26:18+00:00

Sebastian Thiel
byronimo@gmail.com

2015-01-06T17:26:18+00:00

de96c522ff20fa99d13128784a393b619dd0b33b

Now we deal with memory views as well ...





Now we deal with memory views as well ...







A minor fix after porting git-python over to PY3
2015-01-06T14:28:56+00:00

Sebastian Thiel
byronimo@gmail.com

2015-01-06T14:28:56+00:00

b1c9d3eb5b13f2feecb242701f5b4842184f6234

It doesn't do anything (in terms of fixing an issue), but it should be more correct than what was there previously





It doesn't do anything (in terms of fixing an issue), but it should be more correct than what was there previously







Applied autopep8
2015-01-04T10:21:36+00:00

Sebastian Thiel
byronimo@gmail.com

2015-01-04T10:21:36+00:00

ff7615321ee31d981a171f7677a56a971c554059

autopep8 -v -j 8 --max-line-length 120 --in-place --recursive





autopep8 -v -j 8 --max-line-length 120 --in-place --recursive







reduced usage of force_bytes as clients are expected to pass bytes.
2014-11-13T17:46:49+00:00

Sebastian Thiel
byronimo@gmail.com

2014-11-13T17:46:49+00:00

8ae4e9579a263684c6b760aec2869be480ff22ba

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





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 3
2014-11-13T17:31:17+00:00

Sebastian Thiel
byronimo@gmail.com

2014-11-13T17:31:17+00:00

641b64c9f48139cf06774805d32892012fb9b82d

It's a nice way of saying that there is still one failing, consistently.





It's a nice way of saying that there is still one failing, consistently.







Fixed all applicable lint issues
2014-11-13T11:17:01+00:00

Sebastian Thiel
byronimo@gmail.com

2014-11-13T11:17:01+00:00

b64c771bcb2ec336dd549cfe9d072340c886f3c9












Made sure xrange is used instead of range in python 2
2014-11-13T09:31:45+00:00

Sebastian Thiel
byronimo@gmail.com

2014-11-13T09:31:45+00:00

a8f2f63823324ad76cbb36b0f4115e73c7d9d594

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





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