delta/python-packages/gitpython.git/git/cmd.py, branch 2.0.4

Use proper syntax for conditional expression

2016-05-26T21:51:19+00:00

(instead of abusing the "short-circuit" property of logical operations)

fix(remote): use universal_newlines for fetch/push

2016-05-26T17:41:00+00:00

That way, real-time parsing of output should finally be possible.

Related to #444

import OrderedDict from git.odict rather than directly from collections, to pix Py2.6 compatibility

2016-05-26T06:52:30+00:00

fix(cmd): fix with_stdout implementation

2016-05-24T15:52:55+00:00

Admittedly this fix is solely based on the documentation provided
for this parameter, which indicated a different intend than was
actually implemented. Also I don't believe doing this will cause
any harm.

As a special note: the call to `open(os.devnull, 'wb')` does not seem leak
the handle, apparently it is given as-is to the subprocess, which will then
close it naturally. This was tested using an interactive session via `htop`
on osx.

Fixes #437

fix(cmd): don't catch progress handler exceptions

2016-05-24T13:55:40+00:00

Fixes #435

Fix order of operators before executing the git command

2016-05-12T15:43:59+00:00

Since Python 3.3, the hash value of an object is seeded randomly, making it
change between each call. As a consequence, the `dict` type relying on the hash
value for the order of the items upon iterating on it, and the parameters
passed to `git` being passed as `kwargs` to the `execute()` method, the order
of parameters will change randomly between calls.

For example, when you call `git.remote.pull()` in a code, two consecutives run
will generate:

1. git pull --progress -v origin master
2. git pull -v --progress origin master

Within the `transform_kwargs()` method, I'm promoting `kwargs` into an
`collections.OrderedDict` being built with `kwargs` sorted on the keys.
Then it will ensure that each subsequent calls will execute the
parameters in the same order.

Support repeated kwargs

2016-04-19T19:47:45+00:00

Some Git command line options are allowed to be repeated multiple times.
Examples of this are the -C flag which may occur more than once to
"strengthen" its effect, or the -L flag on Git blames, to select
multiple blocks of lines to blame.

    $ git diff -C -C HEAD~1 HEAD
    $ git blame -L 1-3 -L 12-18 HEAD -- somefile.py

This patch supports passing a list/tuple as the value part for kwargs,
so that the generated Git command contain the repeated options.

Make sure .read() and friends always return bytes

2016-04-06T15:12:23+00:00

fix(cmd): Use buffered reads

2016-02-25T03:39:18+00:00

Popen defaults to using unbuffered reads, which are extremely slow.

fix(cmd): allow improved errors during clone operation

2016-02-14T17:22:28+00:00

Related to #383