-
Notifications
You must be signed in to change notification settings - Fork 273
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
Port _SixMetaPathImporter to Python 3.10 #343
Conversation
The failure in CI is caused by the typing module which is not compatible with Python 3.3 but all other tests look good. I can also confirm that this patch works well with Python 3.10 and fixes all tests previously failing due to the warning. We are already testing this patch in Fedora and I can confirm that more than a hundred packages are okay with it with Python 3.9. |
LGTM, but I don't have a lot of context around it. |
Because this is such a weird loader the patch LGTM as a way to make it function appropriately. |
I can confirm that more than 5 hundred RPM packages build fine with six with this patch. |
@benjaminp: Thanks for the update. Tests still pass ;-) |
Thanks for the merge :-) |
`mkdocs` v1.2.0 makes use of `ghp_import` v2.1.0 which in turn makes use of `dateutil` which makes use of the `six.moves` module. The way this module is generated in `six` v1.11.0 is not compatible with Python 3.10+. This gets fixed in v1.16.0 (see benjaminp/six#343).
`mkdocs` v1.2.0 makes use of `ghp_import` v2.1.0 which in turn makes use of `dateutil` which makes use of the `six.moves` module. The way this module is generated in `six` v1.11.0 is not compatible with Python 3.10+. This gets fixed in v1.16.0 (see benjaminp/six#343).
`mkdocs` v1.2.0 makes use of `ghp_import` v2.1.0 which in turn makes use of `dateutil` which makes use of the `six.moves` module. The way this module is generated in `six` v1.11.0 is not compatible with Python 3.10+. This gets fixed in v1.16.0 (see benjaminp/six#343).
`mkdocs` v1.2.0 makes use of `ghp_import` v2.1.0 which in turn makes use of `dateutil` which makes use of the `six.moves` module. The way this module is generated in `six` v1.11.0 is not compatible with Python 3.10+. This gets fixed in v1.16.0 (see benjaminp/six#343).
Fixes #341.