[Distutils] Adding entry points into Distutils ?

P.J. Eby pje at telecommunity.com
Fri May 8 01:24:28 CEST 2009

At 10:21 AM 5/8/2009 +1200, Noah Gift wrote:
>1.  Different versions of Python conflict with previous versions of
>console scripts.  Take paste for example.

I don't understand what you mean.

>2.  The entry point mechanism IIRC recursively scans the site-packages
>directory and loads up the system path with eggs.  This is too
>expensive of an operation for the current environment I work in.

The scan is not recursive; only files that are actually *on* sys.path 
are scanned: i.e., either an .egg that is directly on sys.path, or an 
.egg-info in a directory that is directly on sys.path.

Now, it's possible that some application you are using does such a 
scan explicitly; I'm just noting that merely querying or loading 
entry points doesn't cause any recursive scans, and it most 
definitely does not add anything new to sys.path, unless the entry 
point to be loaded has declared an additional dependency that's *not* 
on sys.path yet.

>3.  There doesn't seem to be a clean way to inject user specific
>environment details to the console script.
>I often need the ability to alter the sys.path in a user specific way
>for the entry point without needing to mess up the global sys.path

I don't understand what you mean here, either.

More information about the Distutils-SIG mailing list