Removed Python 2 jobs #126
Conversation
|
If we merge this now, what would we need to do if we need to do a 6.2.x point release for Python 2.7? Should we tag this master with |
|
I might have made a comment about point releases being rare, but then python-pillow/Pillow#4110 suggested one, so never mind. On the other hand, if PR python-pillow/Pillow#4109 is merged, then the 2.7 wheels CI jobs will start failing. |
radarhere
force-pushed
the
python
branch
2 times, most recently
from
b5620ea
to
9e56047
Compare
|
Actually, pillow-wheels 2.7 latest has already started failing - https://travis-ci.org/python-pillow/pillow-wheels/builds/602789711 |
|
"Latest" is off the master branch, which no longer supports Python 2.7, right? If we needed to do a 6.2.2 security release for 2.7, that would be from the So we could exclude the 2.7/latest jobs here. Or merge this, and if we do need to do a 6.2.2 (hopefully won't happen), we can always reinstate these 2.7 builds. What do you think? |
|
We're now halfway towards the next release, and the odds of 6.2.2 gradually decrease as time goes on - we haven't made a patch release after the first month in the last three years. I think it might be more valuable to merge, to allow better visibility for true failures. If 6.2.2 occurs, then we can work to involve 2.7 builds for that. |
|
Sounds good, thanks! |
See python-pillow/Pillow#3642