[Catalog-sig] Python Version support in PyPI

[Monty Taylor]

On 02/27/2013 02:05 PM, Donald Stufft wrote:
> On Wednesday, February 27, 2013 at 2:03 PM, Monty Taylor wrote:
>> Hey all,
>>
>> OpenStack recently ran in to a problem where one of our depends released
>> a new version that only works with Python 3 and not Python 2. While I
>> wholeheartedly support the gusto of that, and also can't wait until we
>> can move to Python 3, there's a tooling issue here.
>>
>> If I'm doing pip install pyparsing from python2, the system should have
>> enough information to be able to tell whether or not it's going to be
>> getting something that's just fundamentally incompatible - such as a
>> version that does not support python2.
>>
>> I recognize that it would require the package in question marking itself
>> as not supporting python2 ... but let's face it, as we start doing this
>> py2-py3 transition in earnest, it's a pretty important piece of metadata
>> to know about - and I can't imagine we're going to be the only people
>> running in to the problem.
>>
>> Anybody got any thoughts on ways we can help with this that won't suck?
>>
>> Monty
>> _______________________________________________
>> Catalog-SIG mailing list
>> Catalog-SIG at python.org <mailto:Catalog-SIG at python.org>
>> http://mail.python.org/mailman/listinfo/catalog-sig
> The newer peps have support for this via a requires_python field but
> the older tools do not support this field. You'll need to version constrain
> your downloads manually to remove versions you know are not Py2.

Yeah - that's what we're doing now - I think we're just looking towards
trying to prevent breakage systemically where we can.