| Age | Commit message (Collapse) | Author |
|---|
|
W291 trailing whitespace
|
|
E261 at least two spaces before inline comment
|
|
E201 whitespace after '('
E202 whitespace before ')'
E203 whitespace before ':'
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E227 missing whitespace around bitwise or shift operator
E228 missing whitespace around modulo operator
E231 missing whitespace after ','
E241 multiple spaces after ','
E251 unexpected spaces around keyword / parameter equals
|
|
E301 expected 1 blank line, found 0
E302 expected 2 blank lines, found 1
E303 too many blank lines (n)
|
|
W191 indentation contains tabs
E221 multiple spaces before operator
E222 multiple spaces after operator
E225 missing whitespace around operator
E271 multiple spaces after keyword
W292 no newline at end of file
W293 blank line contains whitespace
W391 blank line at end of file
|
|
Merge all fixes from https://github.com/gitpython-developers/GitPython/pull/134
|
|
johnsca-sf-master
Conflicts:
git/cmd.py
git/objects/commit.py
git/objects/fun.py
git/objects/util.py
git/remote.py
git/repo/base.py
git/test/lib/helper.py
git/test/test_commit.py
git/test/test_fun.py
git/util.py
|
|
tox commands now have {posargs} as argument
|
|
Lint setup.py
|
|
Pass flake8 on setup.py. I have left behing the 'line too long' errors
though since they are usually controversial.
The setup() call has been reindented to save a level of indentation.
|
|
When invoking an environement, one might want to pass extra argument to
the command. That is done in tox by invoking an env and passing the
extra arguments after '--' which are then available as '{posargs}'.
Examples:
# Reports flake8 error statistics
tox -eflake8 -- --statistics
# Only run test_util.py tests, printing a line per test:
tox -epy27 -- --verbose git/test/test_util.py
|
|
[skip ci]
See https://github.com/gitpython-developers/GitPython/issues/186 for
the motivation of this fix.
|
|
The lines were added in commit b38020ae , and I might consider a patch release soon
or get ready with 0.3.3. Lets hope not too many installations will be affected.
|
|
Changed motivated by https://github.com/gitpython-developers/GitPython/pull/52
|
|
[skip ci]
|
|
syabro-patch-1
Note by Sebastian Thiel: Was already fixed
Conflicts:
git/refs/reference.py
|
|
GPG signature support on commit object.
|
|
Make tox available, see https://github.com/gitpython-developers/GitPython/pull/179
[skip ci]
|
|
Conflicts:
README.md
requirements.txt
setup.py
|
|
|
|
It represents the latest state on github, which should be better than
what's installed by default.
[skip ci]
|
|
|
|
Merged fd leaks fix from the master to the 0.3 version
|
|
Ensure consistent output from git command
|
|
Fix issue #41: repo.is_dirty() on empty repository with stashed files
|
|
Fix the `git version` parser.
|
|
GitRunCommand exception can store stdout output too.
|
|
0.3 with unicode fixes
|
|
Signed-off-by: David Black <dblack@atlassian.com>
|
|
https://github.com/gitpython-developers/gitdb.git .
Signed-off-by: David Black <dblack@atlassian.com>
|
|
(cherry picked from commit ca2b901e7229fc5c793762fd4e4c1c38c5a78e80)
|
|
(cherry picked from commit 8fa25b1cd5a82679c7b12d546b96c30cafed0559)
Signed-off-by: David Black <dblack@atlassian.com>
Conflicts:
git/test/test_git.py
|
|
Some git commands, like git merge outputs their problems onto stdout,
instead of stderr, which will be thrown away by the current setup. This
change allows the GitPython commands to store the stdout's value too,
in case of error.
|
|
|
|
|
|
Originals:
Pull request "GPG signature support on commit object" #124 by Tatsuki Sugiura.
https://github.com/gitpython-developers/GitPython/pull/124
commit 8065d2abdbb18e09560fc061807301b4c834d5a7
commit 62ecd6c66a84144632b045696326af503ee8cd4e
|
|
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
|
|
Most people know about pep8 which enforce coding style. pyflakes goes a
step beyond by analyzing the code.
flake8 is basically a wrapper around both pep8 and pyflakes and comes
with some additional checks. I find it very useful since you only need
to require one package to have a lot of code issues reported to you.
This patch provides a 'flake8' tox environement to easily install and
run the utility on the code base. One simply has to:
tox -eflake8
The env has been added to the default list of environement to have
flake8 run by default.
The repository in its current state does not pass checks but I noticed a
pull request fixing pep8 issues. We can later easily ensure there is no
regression by adjusting Travis configuration to run this env.
More informations about flake8: https://pypi.python.org/pypi/flake8
|
|
tox https://pypi.python.org/pypi/tox is a thin wrapper around virtualenv
which let you craft a fresh python environement to execute command in.
It creates the env with virtualenv, install dependencies, run python
setup.py install in it and then execute whatever command you want it to
do and report status.
To do so I simply:
- listed tests dependencies in test-requirements.txt (which are just
nose and mock)
- provide a tox.ini file which describe how to install the dependencies
and execute nosetests
- added the module 'coverage' to the list of test dependencies
To run tests simply:
pip install tox && tox
That will execute the test command 'nosetests' using python2.6 and then
python 2.7.
The additional env 'cover' can be run using: tox -ecover.
|
|
More and more packages are listing their dependencies in
requirements.txt which make it trivial to maintain and install them.
|
|
Update README.md to use fixed date
|
|
Relative dates are not that precise, so instead of 3 years ago
set it the last release date to July 2011.
|
|
See https://github.com/gitpython-developers/GitPython/issues/172 for
more information
|
|
As relative paths are used througout, it will work for everyone using
sublime text out of the box.
|
|
Support multiple refspecs in fetch.
|
|
Git supports fetching many refs at once - support this in GitPython
too for more efficient operations when selectively mirroring
repositories.
|
|
Improved retrieval of login names on posix systems.
|
|
https://github.com/gitpython-developers/GitPython/commit/f362d10fa24395c21b1629923ccd705ba73ae996
Related to #43
|
|
Changed link to PyPI; fixed minor typos
|
|
|
