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/
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
