Saint Germain wrote:
No lib/python/site-packages are created !
Nor should they. When you use develop eggs, they are added to the
develop-eggs directory.
Yes I understand that, but I wanted to install those eggs to a regular
directory after.
What do you mean "to a regular directory" and what tools do you want to
use to do this installation?
The idea is to have a link between
lib/python/site-packages/mymodule.egg-link
and /home/user/project/mymodule. That way I can't both have a
representative installed environment (using "import mymodule" works in
this environment) and the ability to continue developing on my regular
personal directory.
Er, you appear to be significantly missing the point of buildout: it
leaves site-packages well along. Nothing should go in site-packages, ever...
What is the point to have the develop eggs in the develop-eggs if I'm
not able to use them ?
They'll be usable within any buildout-generated script, same as
everywhere else...
Using pip, if I install a development environment, I end up exactly
with that file (content is the same):
lib/python/site-packages/mymodule.egg-link
buildout!=pip.
Buildout does its work by creating scripts which manipulate sys.path,
virtualenv/pip do it by creating a completely new python environment.
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
