-
Notifications
You must be signed in to change notification settings - Fork 107
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
tests fail under Python 3.8 #63
Comments
Thanks for the report! These errors are probably not that from looking at it. Probably quite easily fixable, but hard to do it well without the CI support. We should look at this once 3.8 releases (or a bit before) |
Yeah, I'm aware Travis CI is limited on what Python versions are available to use. I don't know if you are open to exploring other CI systems, but there are others with more flexibility that would enable you to run tests with 3.8 without waiting for the final release. Many of them let you run tests in any arbitrary container image (i.e. |
Yes, Travis is a bit limited, but it would allow for "3.8-dev". |
@carlwgeorge I basically don't care on which CI it is running. It's just that I don't want to invest too much time into switching the CI. If you want to add it, feel free. Until then, we can probably just add |
Please try supporting 3.8 before it is released. That's one of the reasons why those prereleases exist - so the ecosystem can be prepared for the final release. Should be 3.8-dev #64 |
We still have a year ;) But you're right we should fix it soonish. There's just so much I have to with all the projects... |
3.8 final is scheduled in 7 months.
If you need help with patches from the Fedora Python SIG, let us know. I don't know parso at all, so contributing might be hard, but we can definitively allocate some time for this. We want to start putting 3.8 into Fedora 31 around first beta (end of May). |
Ok after pip didn't work after trying half an hour I just hacked the sys path with a few path files (pip does nothing else anyway)... It's pretty annoying to get Python 3.8 properly running, haha. No offense to anyone. I fixed it now. Python 3.8 might change again, so there might be other issues in the future. But I feel like most things will likely remain the same. I also released it (for other reasons).
I always need help :) If people want to help out, please help with Jedi bugs. |
I noticed that Python 3.8 is at least on your mind due to #47 and #52. However I discovered that the tests do not pass on that version. Using the
python:3.8.0a2
container image from Docker Hub, I cloned this repo, ranpip install -e .[testing]
, thenpytest
, and got many failures.pytest output (click to expand)
I was able to reproduce the same errors using the python38 package in Fedora.
The text was updated successfully, but these errors were encountered: