At 10:07 AM 10/7/2008 -0400, Tarek Ziadé wrote:
The -m feature of setuptools is nice, but it activates one version at
a time, and
this is globlal to Python unless each application is handling the
version switch,
wich is pretty heavy.
With or without the -m switch, scripts installed by
On Tue, Oct 7, 2008 at 2:42 PM, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 10:07 AM 10/7/2008 -0400, Tarek Ziadé wrote:
The -m feature of setuptools is nice, but it activates one version at
a time, and
this is globlal to Python unless each application is handling the
version switch,
wich is
Tarek Ziadé wrote:
On Tue, Oct 7, 2008 at 2:42 PM, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 10:07 AM 10/7/2008 -0400, Tarek Ziadé wrote:
The -m feature of setuptools is nice, but it activates one version at
a time, and
this is globlal to Python unless each application is handling the
version
At 02:58 PM 10/7/2008 -0400, Tarek Ziadé wrote:
On Tue, Oct 7, 2008 at 2:42 PM, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 10:07 AM 10/7/2008 -0400, Tarek Ziadé wrote:
The -m feature of setuptools is nice, but it activates one version at
a time, and
this is globlal to Python unless each
Phillip J. Eby wrote:
I think we need a standard for tools
interop (ala WSGI), not implementation tweaks for the existing tools.
Agreed.
4/ let's change PyPI to make it work with the new metadata and to
enforce a few things
Enforcements:
- a binary distribution cannot be uploaded if a
At 04:18 PM 10/3/2008 +0100, Chris Withers wrote:
Phillip J. Eby wrote:
It could only do this for specific binaries, since dependencies can
be dynamic.
They should not be dynamic :-(
Too bad. They are, because they have to be in order to support more
than one platform and/or Python version
On Wed, Oct 1, 2008 at 8:10 AM, Tarek Ziadé [EMAIL PROTECTED] wrote:
8/ the requires-python field is rarely used by people, so unless you
try the package, you don't know when it is a source
distribution, if it is going to run on various python versions.
What requires-python field?
I don't
