-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility problem with Python 3.9? #102
Comments
Interesting. I suspect this is more due to a Git update than caused by the Python upgrade. I use Python 3.8 locally and tests started to fail for me too. I'll look into this… |
Seems like this is related to gitpython-developers/GitPython#1014 which in turn is caused by git/git@d18c950 which was published in Git v2.27.0. The issue has been fixed in GitPython v3.1.3 but we're using GitPython 2.x. Updating to GitPython 3.x means dropping Python 2 support. So I'll publish a release that drops Python 2 support in order to fix this issue. |
Thank you! That will work well for us as we don't support Python 2 in Fedora anymore. |
Should be fixed with v2.0.0 🙃 |
I don't see setup.py in the new release tarball? |
Oh, weird. I forgot to publish the release to PyPI. The release there should contain the |
Ah, that makes sense. Thanks! I was unaware that Poetry did that. I'll work on packaging 2.0.0 for Fedora. |
OK, I'm working on packaging, and I've run a super-minor test problem (init.py in tests/ doesn't seem to have % nosetests-3
Is this another case of "the output changed" or is it something more significant? |
That's strange. Seems like this is the exact issue that you had at the start. Could you post the output of running |
Which is interesting, because the package claims to be 3.1.0: Clearly the package is installing 3.0.9 though: |
It appears we're past the initially reported issue, so I'm ready to close this (Fedora mislabeling a package version isn't really your problem). I see you also loosened the dependency on colorama. Thanks! Would you please consider adding the |
Where is it missing? As far as I can tell, the tests run without errors |
When I run I get this error:
I do not see an |
Funny! Since PyGitUp 2.0 I switched to PyTest for running the tests and there everything runs fine. But running with nosetests throws an exception as in your example. I'll publish a post-release with a fix |
This should be fixed now with v2.0.1.post1 |
Excellent! Thanks. |
Hello,
I'm the maintainer of git-up in Fedora. Recently we did a mass archive against Python 3.9 and git-up's test started failing. Here's the relevant log:
I'm not sure why there would be a different hash here. Do you think this might be due to a change in Python 3.9?
The text was updated successfully, but these errors were encountered: