| Age | Commit message (Collapse) | Author |
|
The git command output can vary by language which would cause assertions
errors when parsing the output.
On POSIX system the language used by git can be adjusted by LC_MESSAGES.
The special language 'C' is guaranteed to be always available and is
whatever default the software has been written in (usually english, the
case for git).
Thus passing LC_MESSAGES to Popen will ensure we receive from git a
consistent output regardless of the user preference.
Addresses #153
|
|
Add __call__ method to Git object to allow
passing git command options to the executable
requires flag to transform_kwargs
add unit test
Change-Id: If1bc01008e66d3fd3811c15b56e58f38c95b9887
|
|
Add __call__ method to Git object to allow
passing git command options to the executable
Change-Id: If1bc01008e66d3fd3811c15b56e58f38c95b9887
|
|
When command run as subprocess, AutoInterrupt will kill the
process on destructor. However, if process already finished,
it raise OSError exception.
This fix just ignore OSError on os.kill.
Conflicts:
git/cmd.py
|
|
Currently if command is called with as_proces=True, pipes for the
command will not be closed.
This change makes sure to close command file descriptors.
Conflicts:
git/cmd.py
|
|
probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
|
|
By adding `shell=True,` to the list of Popen parameters, we avoid spawning console windows when scripts call this method from a windowless (.pyw) Python script.
|
|
|
|
installation puts it into the path, instead of git.exe. Of course we warn about the performance penalty that goes with it. Fortunately, using a wrapped git.exe works when creating pipes to the process, admittedly I was a bit surprised by this.
fixes #26
|
|
|
|
thanks to the rpartition method. omg
|
|
|
|
|
|
including test
|
|
the error was caused by PySide which, when instantiating a QApplication, changed the signal handlers to interrupt, instead of retry operating system calls, which caused git-python to fail subsequently. signal.siginterrupt can be used to fix this behaviour after an QApplication was instatiated.
|
|
specific subprocess bug occurs.
|
|
"sleep()".
|
|
adjusted
|