| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
`exc` is private to the module. Naming it `_exc` eliminates a collision
with the `exc` submodule (one which would not be observable at runtime
due to the import failing, but which confuses linters).
|
| |
|
|
|
|
| |
This reverts commit a7c5d887e943aa51f2270e517954c024a8c01500.
|
|
|
|
| |
`flake8` seems to dislike the formatting of black.
|
|
|
|
|
| |
That way people who use it won't be deterred, while it unifies style
everywhere.
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 53d94b8091b36847bb9e495c76bb5a3ec2a2fdb5.
The reason for the revert is that the commit in question introduced a
regression where certain modules, functions and classes that were
exposed before were no longer exposed.
See https://github.com/gitpython-developers/GitPython/pull/1352#issuecomment-932757204
for additional information.
|
|
|
|
|
|
|
| |
All `from <module> import *` has now been replaced by
`from <module> import X, Y, ...`.
Contributes to #1349
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #1002
|
|
|
|
|
|
|
|
|
| |
This is related to my fix in #658. Apparently, MacOS adds a git
executable that is just a stub which displays an error. This gets past
the try/except I added in #658, and allows all of the GitPython
components to be imported, but since the executable is not *actually*
git, it results in an exception when ``refresh()`` attemepts to run a
``git version``.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This catches any raise of one of the custom exceptions defined in
`git.exc` during the imports in the dunder init, and raises an
`ImportError` in those cases.
|
| |
| |
| |
| |
| |
| |
| | |
Added additional information in the import warning/error that tells the
user how to silence the warning/error. Also added a GIT_OK variable
that allows for a quick check whether the refresh has succeeded instead
of needing to test an actual git command.
|
| |
| |
| |
| |
| |
| | |
Renamed to simplify and avoid issue with nose tests trying to use
`setup` as a setup for testing. Unittest implements basic test for
refreshing with a bad git path versus a good git path.
|
|/
|
|
|
|
|
|
| |
Discovered that the remote module also relies on the git executable as
such it also needs to be “refreshed” anytime the git executable is
updated or changed. This was best solved by moving the setup function
into the top level __init__ where the setup simply calls
git.cmd.Git.refresh and git.remote.FetchInfo.refresh.
|
|
|
| |
Usecase described in #553
|
| |
|
|
|
|
|
|
|
|
| |
+ Mark all unused vars and other non-pep8 (PyDev) warnings
+ test_utils:
+ enable & fix forgotten IterableList looped path.
+ unittestize all assertions.
+ remote: minor fix progress dispatching unknown err-lines
|
|
|
|
|
| |
Previously it would always adjust your system path, which is bad
behaviour.
|
| |
|
|
|
|
|
| |
Commandline was
autopep8 -j 8 --max-line-length 120 --in-place --recursive --exclude "*gitdb*,*async*" git/
|
|
|
|
| |
W291 trailing whitespace
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
|
|
|
|
|
|
| |
tests may work.
Switched gitdb submodule to new github url
|
|
adjusted
|