[Catalog-sig] Finalising PEP-345 - Requires-Python

Noah Kantrowitz noah at coderanger.net
Thu Dec 31 03:13:12 CET 2009


> -----Original Message-----
> From: catalog-sig-bounces+noah=coderanger.net at python.org
> [mailto:catalog-sig-bounces+noah=coderanger.net at python.org] On Behalf
> Of Ben Finney
> Sent: Wednesday, December 30, 2009 6:10 PM
> To: catalog-sig at python.org
> Subject: Re: [Catalog-sig] Finalising PEP-345 - Requires-Python
> 
> David Lyon <david.lyon at preisshare.net> writes:
> 
> > > Requires-Python: 2.5
> > > Requires-Python: >2.1
> > > Requires-Python: >=2.3.4
> > > Requires-Python: >=2.5,<2.7
> >
> > I think most untrained readers, would find the ">=2.5,<2.7" notation
> > to be non-obvious and ambiguous.
> >
> > The shortest known method to express the condition is
> > "Requires-Python: 2.5:2.7"
> 
> Again, it's a poor assumption that the dependency specifications will
> be
> read as though they follow the rules of Python syntax. The colon
> doesn't
> obviously mean what you're wanting it to mean in that context. Please
> lose the Python-language bias when assessing these issues.

Also while the metadata should really have Only One Representation, it isn't directly user facing. A packing index could easily display it in a different way (icons?) and a packager could accept more than one input syntax.

--Noah



More information about the Catalog-SIG mailing list