On Tue, 2015-12-22 at 22:43 -0500, Alex Gaynor wrote: > Hi all, > > I'd like to propose we formally deprecate (in our next release) and remove > (in the release thereafter) support for Python2.6. > > It is no longer under support from its developers (which makes it a > security risk), its use is more or less confined to users of CentOS and > RHEL (which means SCL is available to them, and they have a corporate > benefactor to complain to if it doesn't work), and its seriously funking > with our development workflow because it's so abysmally slow in CI (which > means it's annoying me enough to want to solve this). > > There is genuinely no justifiable reason to use Python 2.6 anymore, both > Django and Twisted have dropped it. > > If this would _seriously_ impact you, please reply to this thread. If > possible I'd also like to hear from our downstreams.
We do not build python-cryptography for RHEL 6 so we do not have a strong reason to ask for 2.6 support. I can't speak for potential customers that may have a different opinion and build it themselves. Simo. -- Simo Sorce * Red Hat, Inc * New York _______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
