delta/python-packages/gitpython.git/git/config.py, branch winerr_show

FIX config-lock release early regression caused by #519

2016-10-02T22:37:37+00:00

+ Regression introduced in d84b960982b, by a wrong comment
interpretation.

RF: use @functools.wraps within decorators instead of manual name reassignment

2016-10-02T15:17:36+00:00

@wraps does more and does it right ;)

cfg_TCs, #519: FIX config resource leaks

2016-10-01T02:15:25+00:00

+ Modify lock/read-config-file code to ansure files closed
+ Use `with GitConfigarser()` more systematically in TCs.
+ Clear any locks left hanging from pev Tcs

config parsers as context mangers can now be reentered for locks

2016-03-06T15:47:44+00:00

enable config parsers to be used as context managers

2016-02-20T21:09:31+00:00

if used as context managers, the parsers will automatically release their file locks.

fix(cmd): prevent deadlock on clone/fetch/pull

2016-02-07T11:20:04+00:00

We keep stdout closed, which seems to have the side-effect of
stdout being connected to your TTY, in case you run a terminal.

However, this shold also prevent deadlocks, as only stderr is used.
The alternative would have been to try to fetch lines concurrently,
and we have been there.

For clone(), `communicate()` is used, and with some luck this will
just do the right thing. Even though last time I checked, it
didn't ... ? Lets see.

Stab at #72

fix(config): ignore empty values in config file

2015-09-06T13:11:54+00:00

Similar to git, we now ignore options which have no value.
Previously it would not handle it consistently, and throw a parsing
error the first time the cache was built.

Afterwards, it was fully usable though.
Now we specifically check for the case of no-value options instead.

Closes #349

fix(config): use `str.startswith('~')` instead of `'~' in str`

2015-07-06T13:43:47+00:00

fix(config): care tilde in include.path config

2015-07-06T12:00:54+00:00

Added NullHandlers to all loggers to preven "No handler" messages

2015-06-25T13:24:40+00:00

When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.