-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Tests failed with python3.8.0a1 #4716
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
Comments
thanks for trying and getting us a early pointer about python 3.8 compatibility At first glance it seems all to come down to minor differences in ast for the assertion rewriting which is a great starting point, it should be relatively straightforward to sort out the issues on time. As of now i cant tell which of those are intended updates of the ast and which are python alpha issues that will go away themselves - the tracking issue here and over in the python tracker will be a great tool to stay on top of it. 👍 |
after taking a glance at the detail issues in the python tracker it seems that the ast provides various rock-solid extra metadata elements that will allow us to ensure MUCH more solid statement range finding, |
hi @RonnyPfannschmidt no problem, I think I will create a CI for the most used libraries and Python 3.8.0aX and will create an issue for each library, maybe I will help the community with this CI. Have a nice day. |
@RonnyPfannschmidt cool nice news. |
Is there a stacktrace for this? I'm having trouble finding the failure mode and what triggers it -- can it be edited into the original message here and/or on the bpo issue? |
Hi,
I have tried to execute the tests with the new alpha release of Python 3.8
https://www.python.org/downloads/release/python-380a1/
And I get some errors, maybe it's an issue with pytest or with pytest but I have created an issue on the bug tracker of Python (https://bugs.python.org/issue35895)
tox-pytest-38-stdout.log
The text was updated successfully, but these errors were encountered: