Excerpts from Jeremy Stanley's message of 2015-07-13 11:57:35 +0000: > On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote: > > clients and oslo libraries still maintain their py26 for a reason: > > decision to drop py26 was for server projects only. > > Yes, that decision was made at a time when our server projects had > stable branches, but our clients and shared libraries did not. My > recollection is that "server projects only" was a proxy for "only > projects with stable branches." Now that we have stable branches of, > say, python-novaclient where we can backport juno-relevant security > fixes, people on 2.6-only platforms who want to install and run > python-novaclient from PyPI can use the stable/juno version (though > I'll admit that finding which version works with 2.6 may be a tricky > proposition for a consumer who is unaware of this situation).
Yes, that's my recollection, too. I'm also a bit worried about the PyPI situation, since pip doesn't automatically detect that a version of a package is incompatible with the current version of python. The etherpad Dims linked to [1] proposes looking at the PyPI stats for client downloads. If those look relatively low, I would feel more confident in dropping 2.6 support in the master branch of the clients, with major version updates to indicate that. On the other hand, how much longer will we be supporting Juno? A matter of months, right? Doug [1] https://etherpad.openstack.org/p/juno-cross-project-future-of-python __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
