[Distutils] Disabling --single-version-externally-managed

Toshio Kuratomi a.badger at gmail.com
Sat Sep 1 21:29:54 CEST 2007

Hash: SHA1

Phillip J. Eby wrote:
> At 06:56 PM 8/31/2007 -0700, Toshio Kuratomi wrote:

>> I tried manually creating a .pth file that lists one or the other of the
>> eggs.
> That won't work to make the egg the default version.  You have to have
> easy_install generate the .pth file, so that the necessary magic is
> included.
> Normally, paths in .pth files are added to the *end* of sys.path, which
> means the single-version egg will take precedence.  easy_install adds
> special incantations to its .pth files so that the eggs it installs have
> higher precedence than everything else.
Good to know.  It doesn't affect what I tested as I used a manually
created .pth file *instead* of using single-version-externally-managed.
 So the eggs were arranged as:
  sqlalchemy.pth (containing the path into one of the eggs)

I'd rather do without .pth's in the Guidelines though, as they seem to
duplicate what can already be achieved by installing one egg as

The rest of this is miscommunication based on my using terms
incorrectly.  I'll reply to the other message with something meaningful
now that I understand:

active version -- egg on sys.path

inactive version -- egg cannot be found by python as it is not on sys.path

default version -- version of a module that comes first on sys.path and
therefore will be selected from a bare import

project -- setuptools managed project that uses requires.txt to manage
conflicting versions.

If I've still got those wrong, let me know :-)

- -Toshio
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the Distutils-SIG mailing list