Closed JPTeasdale closed 1 year ago
I guess the simplest solution is to drop support for 3.4 ourselves, too? (Or at least stop advertising that we support it and stop running the tests for it). @mauritsvanrees?
The above error should be fixable by first doing pip install colorama
with a version constraint that still works.
I am fine with dropping 3.4 support. I am not using it.
Actually:
.travis.yml
does not test it. It tests 2.7, 3.5, 3.6, and pypy.tox.ini
tries to test with 3.3+, but I am not using it, might be outdated (could be useful though).setup.py
claims 2.7 and 3.5+ and PyPy in the classifiers.So it seems we do not have to do anything (except maybe cleanup tox.ini
).
For me personally (and the Plone community in general):
setuptools
does not support it. So it is understandable if we drop this at some point this year. But preferably not.I'm closing the issue, we don't support 3.4 anymore :-)
Looks like colorama dropped support for Python 3.4 which means that
pip install zest.releaser
breaks on python 3.4 as well.