-
Notifications
You must be signed in to change notification settings - Fork 16
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
Drop Python 3.6 support? #178
Comments
Looks good to me :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
plone52-py36
job currently fails, probably because I released Plone 5.2.11 yesterday.Sample failure:
This is the kind of version conflict that I am not solving anymore in Plone coredev 5.2 for Python 3.6: this Python version is out of support, and Plone dropped support already in 5.2.10.
I propose that we drop support for python 3.6 in
collective.exportimport
.@pbauer Would that be okay with you?
Workaround might be to add something like this, but it is untested and could give a different conflict:
The text was updated successfully, but these errors were encountered: