No you're not right here. With buildout, when you are using the develop clause, it create a link in the develop-eggs dir and if look inside the new file it would point to your package directory directly.
After that you can install the egg in the "eggs' section and use it directly as it would be installed from pypi.
is it working correctly ?
On Thu, Mar 18, 2010 at 2:05 PM, Saint Germain firstname.lastname@example.org wrote:
I'm trying to use buildout with develop eggs, but it seems that they cannot be installed.
Here is the scenario :
I create a simple project in /home/user/project mkdir mymodule touch mymodule/__init__.py echo -e "from setuptools import setup\nPACKAGE = 'mymodule'\nVERSION = '0.1'\nsetup(name=PACKAGE, version=VERSION, packages=['mymodule'] )" > setup.py
- I use the following buildout.cfg
[buildout] develop = /home/af79141/project parts = eggs
[eggs] recipe = zc.recipe.egg eggs = mymodule
- I copy bootstrap.py in the directory
I end up with the following content: bin bootstrap.py buildout.cfg develop-eggs eggs parts
No lib/python/site-packages are created ! But there is a file mymodule.egg-link in develop-eggs with the following content: /home/users/project . What am I doing wrong ? I was expecting a created file like lib/python/site-packages/mymodule ?
Thanks in advance,
Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig