| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
|
|
|
|
Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
|
|
[skip CI]
|
|
And directly use coverage.py
|
|
|
|
Ubuntu Xenial 16.04 is now the default Travis CI build environment:
https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment
|
|
This reverts commit 913d806f02cf50250d230f88b897350581f80f6b.
|
|
This reverts commit dac619e4917b0ad43d836a534633d68a871aecca.
|
|
Currently `make html` will output pages without styles
or different than the online documentation.
With this change the local documentation looks the same as the online
documentation.
|
|
Fixes #312
|
|
This reverts commit 74a0507f4eb468b842d1f644f0e43196cda290a1.
https://travis-ci.org/gitpython-developers/GitPython/jobs/561334516#L634
|
|
|
|
|
|
|
|
|
|
Running "nightly" on trusty (the current default on travis) is not
nightly any more, but 3.7.0a4+. See
https://docs.travis-ci.com/user/languages/python/#development-releases-support
|
|
|
|
|
|
|
|
It really is not supported anymore by anyone, so it seems.
|
|
|
|
Add more recent Python versions including development branches and nightly build.
|
|
Details:
- Added Python 2.6 again to .travis.yml (it was removed in commit 4486bcb).
- Replaced the use of dictionary comprehensions in `git/cmd.py` around
line 800 with the code before that change (in commit 25a2ebf).
Reason: dict comprehensions were introduced only in Python 2.7.
- Changed the import source for `SkipTest` and `skipIf` from `unittest.case`
to first trying `unittest` and upon ImportError from `unittest2`.
This was done in `git/util.py` and in several testcases.
Reason: `SkipTest` and `skipIf` were introduced to unittest only
in Python 2.7, and `unittest2` is a backport of `unittest` additions
to Python 2.6.
- In git/test/lib/helper.py, fixed the definition of `assertRaisesRegex`
to work on py26.
- For Python 2.6, added the `unittest2` dependency to `requirements.txt`
and changed `.travis.yml` to install `unittest2`. Because git/util.py
uses SkipTest from unittest/unittest2, the dependency could not be added
to `test-requirements.txt`.
- Fixed an assertion in `git/test/test_index.py` to also allow
a Python 2.6 specific exception message.
- In `is_cygwin_git()` in `git/util.py`, replaced `check_output()` with
`Popen()`. It was added in Python 2.7.
- Enabled Python 2.6 for Windows:
- Added Python 2.6 for MINGW in .appveyor.yml.
- When defining `PROC_CREATIONFLAGS` in `git/cmd.py`, made use of certain
win32 and subprocess flags that were introduced in Python 2.7, dependent
on whether we run on Python 2.7 or higher.
- In `AutoInterrupt.__del__()` in `git/cmd.py`, allowed for `os` not having
`kill()`. `os.kill()` was added for Windows in Python 2.7 (For Linux, it
existed in Python 2.6 already).
|
|
+ Use environment-markers in requirement files (see
http://stackoverflow.com/a/33451105/548792).
|
|
|
|
Now that performance tests are run, it appears we run into one
particular failure on travis, possibly indicating a bug in python 3.3.
Just bluntly increason the amount of handles might silence it... .
Related to #524
|
|
RF: coveralls (not used/relied on really) -> codecov
|
|
+ Detect code breaking the body of TCs eventually hidden win-errors by
raising SkipTest ALAP.
+ submodule.base.py: import classes from `git.objects` instead of
`utils`.
+ had to ++ ulimit 100->110 for the extra code tested (more leaks :-)
+ Centralize is_win detection.
|
|
+ PY3.3 fails due to 'too many files open"
|
|
codecov in our (datalad, etc) experience provides a better service,
great support, and super-nice intergration with chromium and firefox
for reviewing coverage of pull requests. In light of the
@with_rw_directory fiasco detected/fixed in #521 I would strongly
recommend to (re-)enable and use coverage reports
|
|
+ Extract util-method to delete lock-files, also on Windows (will be
needed by TCs).
|
|
+ Collect all known commands
|
|
+ DataDriven TCs for identifying which separate case failed.
+ appveyor: rework matrix, conda3.4 cannot install in develop mode
|
|
|
|
|
|
|
|
Fixes #478
|
|
|
|
As inspired by comments in #431
|
|
It's just a guess, maybe we are lucky.
The original problem is that travis checks out tags without branches,
and thus checking out master does only work if travis runs on master.
With tags, it will only heckout and locally know the tag in question.
The changes should allow it to retry and create the master branch
instead.
|
|
|
|
In response to
https://github.com/gitpython-developers/GitPython/pull/408/files/5de21c7fa2bdd5cd50c4f62ba848af54589167d0..aae2a7328a4d28077a4b4182b4f36f19c953765b#r59722704
|
|
Just to get the tests green again for py2.7.
Deleting the test isn't the right way to do it, but the one of a
maintainer who wants to spend no more time than possibly necessary.
|
|
|
|
Previously travis would fail to clone the special testing repository
as SSH access requires a deploy key to be set. The latter has been
configured and is now added in clear-text.
This is save as it is only good for read-only access to a test
repository, mis-use cannot happen that way.
|
|
Related to #301
|
|
As it seems to contain custom inforamtion that we want to keep.
Now we are appending to it ...
|
|
* config parser now handles quoted values correctly. This doesn't hamper
multi-line support.
* added regression test to travis to assure we will be warned if we
rewrite and break the user's .gitconfig file
* only rewrite configuration files if we actually called a mutating
method on the writer. Previously it would always rewrite it.
Fixes #285
|
|
original HEAD
|
