-
Notifications
You must be signed in to change notification settings - Fork 101
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
Add preliminary support for Python 3.9a4. #784
Conversation
Great idea. I was thinking of that this morning, too. Travis may be the biggest problem, as always... |
Without these changes even pip --version fails because it cannot import pip. 😞
After fixing
It does not happen locally with the same Python version. |
For what it's worth, I can confirm the tests on Python 3.9 run fine in my macOS sandbox. |
@dataflake Same here. My next steps will be to try AccessControl, ExtensionClass, Persistence, persistent on TravisCI for 3.9 to see if it breaks there, too. |
On a CentOS 7 install the tests run through without issue. The Python interpreter was compiled with |
This has to do with zopefoundation/persistent#124 and zopefoundation/Persistence#22. These issues seem to have been fixed before we can use Python 3.9. So moving the issue to future after Zope 5.0. Preliminary Python 3.9 support should not prevent the Zope 5 release. |
I fully agree. |
# Conflicts: # CHANGES.rst # versions.cfg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests run through without issue now.
No description provided.