[Distutils] virtualenv & pypi-server

[PJ Eby]

On Wed, Oct 26, 2011 at 6:21 AM, Andrea Crotti <andrea.crotti.0 at gmail.com>wrote:

> On 10/25/2011 09:59 PM, PJ Eby wrote:
>
>>
>> If you use the "-m" option to easy_install, the easy-install.pth won't be
>> changed (or even created, if it doesn't exist).  Instead, the application
>> scripts will simply add the needed eggs to their path at runtime.
>>
>> This is the most flexible approach; the only downside to it is if you just
>> start a Python interpreter, none of the eggs will be on sys.path unless you
>> explicitly pkg_resources.require() them.  But for stable app deployment, or
>> even app development (using "setup.py develop" or "setup.py test") it works
>> rather well.
>>
>>
> Thanks a lot, that might be a nice solution.
> Reading the doc I would have never guessed it since "-m" stands for
> multi-version...
>
> Anyway the other problem is that our applications are actually Envisage
> applications (which have plugin
> discovery at run-time) which complicates things a little bit.
> I'll try to make a trivial example and see if it might work...
>
> However, I still need a pypi-server running on localhost to discover all
> the eggs I might need to require, is that correct?


Why would you need that?

As long as the eggs are present in a sys.path directory, the normal
pkg_resources machinery will find them.

If you mean you want to be able to test installation and deployment, or you
are continually rebuilding your install directory for some other reason,
then once again you don't need a PyPI server - just put all the eggs in a
directory somewhere and use the --find-links (-f) option to easy_install to
specify that directory name.  It will then copy them from there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20111026/77291ec9/attachment.html>