On 6/23/06, Mark Nottingham <[EMAIL PROTECTED]> wrote:
> I was thinking more about things where people can search for packages
> that need different versions of python, etc.; not so much for
> automation.
OK, now I see why you need it. I'm sure using virtual package name
"python" to declare python
I was thinking more about things where people can search for packages
that need different versions of python, etc.; not so much for
automation.
On 2006/06/23, at 6:05 PM, Serge Orlov wrote:
> On 6/23/06, Mark Nottingham <[EMAIL PROTECTED]> wrote:
>> I was looking for some normal (hopefully, m
On 6/23/06, Mark Nottingham <[EMAIL PROTECTED]> wrote:
> I was looking for some normal (hopefully, machine-readable) way to
> indicate it so that people can figure out the version of Python
> required before they download the package.
I'm sure writing English text like "make sure you have python 2
Yep, I'm doing that (thanks!).
I was looking for some normal (hopefully, machine-readable) way to
indicate it so that people can figure out the version of Python
required before they download the package.
On 2006/06/23, at 11:04 AM, Serge Orlov wrote:
> On 6/23/06, Mark Nottingham <[EMAIL P
On 6/23/06, Mark Nottingham <[EMAIL PROTECTED]> wrote:
> PEP 314 introduces metadata that explains what packages are required
> by a particular package. Is there any way to express what version of
> Python itself is required?
No, but you can do it yourself:
# do not edit this file, edit actualset
PEP 314 introduces metadata that explains what packages are required
by a particular package. Is there any way to express what version of
Python itself is required?
Cheers,
--
Mark Nottingham http://www.mnot.net/
--
http://mail.python.org/mailman/listinfo/python-list
