Skip to content
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

Pillow >= 4.0.0 vs python 2.6 -- pick one #50

Closed
zimeon opened this issue Jan 20, 2017 · 9 comments
Closed

Pillow >= 4.0.0 vs python 2.6 -- pick one #50

zimeon opened this issue Jan 20, 2017 · 9 comments
Labels

Comments

@zimeon
Copy link
Member

zimeon commented Jan 20, 2017

We can't use the current major version of Pillow (>= 4.0.0) if we still want to support python 2.6 because Pillow v4 drops support. #49 tied pillow to < 4.0.0 but at some stage we should probably drop python 2.6 support -- but this might cause problems for folks with older RedHat/CentOS VMs.

@azaroth42
Copy link
Member

Python 2.6 is the version on the iiif.io server:

[iiif@ip-172-31-44-83 ~]$ python --version
Python 2.6.6

So I think we should pick 2.6 for the moment!

@zimeon
Copy link
Member Author

zimeon commented Jan 25, 2017

I agree that we should support 2.6 for a bit longer, I think the RHEL problem is bigger than just the iiif.io server as it is widely used in institutions like mine. According to Red Hat's lifecycle document, RHEL6 enters its 3rd and final production phase (essentially maintenance only) in May 2017 so hopefully that will mean institutions moving away from RHEL6 and py2.6 this year.

Propose we revisit the question later in 2017.

@hugovk
Copy link
Contributor

hugovk commented Oct 19, 2017

It's now later in 2017.

RHEL 6 and CentOS 6 are still on Python 2.6 (with RHEL 5 still on Python 2.4!):

image

https://en.wikipedia.org/wiki/CPython#Enterprise_Linux

Current pip 9 deprecates Python 2.6 support, and pip 10 won't support it (pypa/pip#3955).

@acdha
Copy link

acdha commented Oct 19, 2017

The EL6 series will never get an upgrade to the core OS but it’s easy to get Python 2.7 or 3.x from RHSCL, IUS Community, etc. See https://access.redhat.com/solutions/92933 for the commercial offering.

Here’s one of the core python developers and a red hat employee on the subject:

http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html

I agree with that - unless there are a lot of people willing to pay for supporting old versions, the enterprise IT shops should be on the hook for their policies’ costs.

@hugovk
Copy link
Contributor

hugovk commented Oct 19, 2017

I think you meant to include this link for the core Python developer:

https://snarky.ca/stop-using-python-2-6/

@acdha
Copy link

acdha commented Oct 19, 2017

Nick and Brett are both core CPython developers; Nick also works at RH so I figured his post was more compatible with their world view

@zimeon
Copy link
Member Author

zimeon commented Oct 19, 2017

I agree with the sense of @hugovk and @acdha posts above, it is time to let 2.6 die and focus on python 2.7 + 3.x.

@hugovk
Copy link
Contributor

hugovk commented Nov 12, 2017

Please see PR #58 and comments welcome. Thank you!

@zimeon
Copy link
Member Author

zimeon commented Dec 13, 2017

iiif.io servers have Python 3.4 now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants