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
python3 compatibility #21
Conversation
So we have a baseline from which to bootstrap python 3 porting while retaining python 2.7 compatibility.
…ccessControl into py3-pure-python
It’s no longer a builtin in python3 anyway.
AccessControl can't support a pure Python version, as the pure Python implementation of Acquisition/ExtensionClass can't be perfect enough and isn't able to proxy class dict proxies.
This currently runs into a problem in both Acquisition.h (which needs zopefoundation/Acquisition#13 to be merged and released, so the aq_init macro uses PyCapsule_Import) and with ExtensionClass.h (zopefoundation/ExtensionClass#14).
…ccessControl into py3-pure-python
# Conflicts: # CHANGES.rst # setup.py # src/AccessControl/Permission.py # src/AccessControl/tests/testZopeGuards.py # src/AccessControl/users.py
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.
LGTM
Changes Unknown when pulling 1b5488a on py3-pure-python into ** on master**. |
1 similar comment
Changes Unknown when pulling 1b5488a on py3-pure-python into ** on master**. |
Now that |
The branch couldn't be deleted, as the other isort PR still wanted to merge commits into it. Since that wasn't going to get accepted as-is, I've closed that other PR and deleted the py3-pure-python branch. |
Not done yet - but easier to talk about in pull request format.
To work on this branch, you will need this patch applied, as none of the RestrictedPython stuff is ready yet.