It looks like CI isn't healthy. Do you want some help with that?

Thanks a bunch for uncovering this, and for the fix!

It looks like one travis failure legit, asit is flake not liking some whitespace.
Theother travis failure looks like it is related to the - now - flaky Remote test, which also fails consistently in#825 .

Please have a look at the comment there - maybe we can make a fix here so#825 can then be merged, too.

CC@cclauss

Codecov Report

Merging#826 intomaster willdecrease coverage by0.12%.
The diff coverage is100%.

@@            Coverage Diff             @@##           master     #826      +/-   ##==========================================- Coverage   94.79%   94.67%   -0.13%==========================================  Files          59       59                Lines        9603     9386     -217     ==========================================- Hits         9103     8886     -217  Misses        500      500

Continue to review full report at Codecov.

Legend -Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing data
Powered byCodecov. Last update1f66e25...21b712a. Read thecomment docs.

Run Python 3.7 inallow_failures mode until#827 is fixed?

What about the windows failures?

FileNotFoundError: [WinError 2] The system cannot find the file specified:    'C:\\Miniconda35-x64\\lib\\site-packages\\setuptools-27.2.0-py3.5.egg'

But the lines just above that say that thecurrent version of setuptools (40.6.3) was just installed. Either don't upgrade setup tools or eliminate the hardcoding of setuptools-27.2.0.

What I was asking is do you want to ignore those too?

I'd prefer to merge this, and then deal with the CI failures, instead of bundling them all together... these changes improve (and fix) the setup.py issues.

You are asking the wrong guy... I have never been a Windows fan. ;-) I would vote to move forward as is.

Do we need the last three windows builds for "miniconda" or "git running in cygwin on windows"? The latter just looks like a test environment failure as it is passing windows paths (from the windows native python 3.5-x64) into a program looking for a unix path. I have no idea what the "conda" ones are or if they provide any real value.

The test suite makes a very bad assumption that you are on the master branch. When I work on a project, I fork it, then I make a branch for each of the changes I am making, and submit pull requests from the branch into the upstream master. This is best practices for github development.

I cannot run the test suite if I have anything else checked out. The test suite fails. It is making some bad assumptions. When I run inside a docker container and skip past those, even with python 3.6, I'm seeing other issues like utf8 issues.

I worked around the issues by checking out a copy of the repository from github into the container at a well-known location. This way the unit tests can run against a fresh clone of the repository and succeed.

I'm going to tease this apart into smaller bits...

@Byron consider merging this. The appveyor jobs are passing, at least the ones known to pass, and there are some that are known failures; it would still be nice to get all the CI builds to green since that makes it so much easier to determine if a pull request is even worth looking into.

Hi@jeking3 , thanks so much for your persistency. Right now I am very short on time and am far away from this, and any other of my open source projects, which must be frustrating for GitPython's user base.

Maybe it would help if there were more collaborators - I have invited you in case this sounds feasible to you.

I'll do what I can. Apart from founding a new company, I'm also involved in boost, apache thrift, and a couple other efforts. At the very least if I can get the CI builds to run clean and have folks rebase their pull requests, it would be a lot easier to qualify things in the pipeline. Thanks!