Unexpected easy_install -zmaxd behavior when package is already installed
Hello, I am using easy_install on windows for its ability to install binary eggs (and compiled extension modules). Also using virtualenv to separate my environments. I want to be able to manage an egg cache to be used in a local installation workflow: download the package and build the eggs in a defined directory. I first download the package using the documented approach of getting the packages built into eggs in a directory: easy_install -zmaxd [my_dir] I would expect to have zipped eggs at the "my_dir" destination. This works as expected only if I start from a clean virtualenv. If the environment is already populated (or installed) with the package I want to cache, it is this package (from site-packages) that is taken to my cache directory, not the zipped egg (I presume because the package is not zip safe). Is there a way around this behaviour? Thank you, D.
On 2012-11-05 16:18:27 +0000, David Genest said:
Hello,
I am using easy_install on windows for its ability to install binary eggs (and compiled extension modules). Also using virtualenv to separate my environments.
I want to be able to manage an egg cache to be used in a local installation workflow: download the package and build the eggs in a defined directory.
E.g. Like what Buildout does for you?
I first download the package using the documented approach of getting the packages built into eggs in a directory:
easy_install -zmaxd [my_dir]
I would expect to have zipped eggs at the "my_dir" destination.
my_dir is not the destination it's the requirement_or_url e.g. Something with a setup.py in it.
This works as expected only if I start from a clean virtualenv.
If the environment is already populated (or installed) with the package I want to cache, it is this package (from site-packages) that is taken to my cache directory, not the zipped egg (I presume because the package is not zip safe).
Is there a way around this behaviour?
I don't fully understand, but I expect this may be normal given the contraints above (i.e. easy_install does not understand what you intend by specifying "my_dir" AFAICT).
Thank you,
D. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Alex Clark ยท https://www.gittip.com/aclark4life/
I want to be able to manage an egg cache to be used in a local installation workflow: download the package and build the eggs in a defined directory.
E.g. Like what Buildout does for you?
Haven't looked at this. Will do, thank you.
I first download the package using the documented approach of getting the packages built into eggs in a directory:
easy_install -zmaxd [my_dir]
I would expect to have zipped eggs at the "my_dir" destination.
my_dir is not the destination it's the requirement_or_url e.g. Something with a setup.py in it.
Sorry, my usage was not complete. If you do: $ mkdir tmp $ easy_install -zmaxd tmp/ pyramid All the packages and dependencies of pyramid will be downloaded locally in the tmp/ directory. As per: http://packages.python.org/distribute/easy_install.html#installing-on-un-net...
This works as expected only if I start from a clean virtualenv.
If the environment is already populated (or installed) with the package I want to cache, it is this package (from site-packages) that is taken to my cache directory, not the zipped egg (I presume because the package is not zip safe).
Is there a way around this behaviour?
I don't fully understand, but I expect this may be normal given the contraints above (i.e. easy_install does not understand what you intend by specifying "my_dir" AFAICT).
For my specific pyramid example above, if the virtualenv I start from is empty, the pyramid and dependencies eggs are put and built in the tmp/ dir. Otherwise, if the environment has pyramid installed, the eggs are unzipped (as they are when installed) in the tmp/ directory.
participants (2)
-
Alex Clark -
David Genest