Closed andy-maier closed 2 years ago
Might have been nice to know why Python 3.4 breaks, but others did all the packaging changes for me in the latest version and isn't obvious what the issue is to me, so have changed python_requires
to only specifically include those versions which automated testing is done for. The 1.13.0 version has been yanked on PyPi and 1.13.1 has the new classifier, so if you remove any pinning of your own you may have added, should now hopefully use <1.13.0 for Python 3.4.
Closing on presumption this is all good now.
Version 1.13.0 released today declares its Python requirements as
!=3.0.*, !=3.1.*, !=3.2.*, >=2.7
. This causes it to be picked by Pip on Python 3.4 as an eligible version. The subsequent installation on Python 3.4 fails with:This can be circumvented by packages using wrapt by pinning it to <1.13 on Python 3.4, but it should be fixed by wrapt by adjusting its "python_requires" attribute in setup.cfg accordingly.