[buildout] Impossible to install develop eggs
Hello, I'm trying to use buildout with develop eggs, but it seems that they cannot be installed. Here is the scenario : 1) 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 2) I use the following buildout.cfg [buildout] develop = /home/af79141/project parts = eggs [eggs] recipe = zc.recipe.egg eggs = mymodule 3) I copy bootstrap.py in the directory ( http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py) 4) python bootstrap.py 5) bin/buildout 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,
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 <saintger@gmail.com> wrote:
Hello,
I'm trying to use buildout with develop eggs, but it seems that they cannot be installed.
Here is the scenario :
1) 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
2) I use the following buildout.cfg [buildout] develop = /home/af79141/project parts = eggs
[eggs] recipe = zc.recipe.egg eggs = mymodule
3) I copy bootstrap.py in the directory (http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py)
4) python bootstrap.py
5) bin/buildout
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
On Thu, 18 Mar 2010 14:13:19 -0400, Mathieu Leduc-Hamel <marrakis@gmail.com> wrote :
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 ?
Hello, I understand what is the meaning of the develop clause and that I should end up with the mymodule.egg-link in the develop-eggs directory Problem is only that I don't manage to install this egg. In the buildout.cfg, I tried to install it but nothing happen (no error message, nothing). I was expecting that: 1) the buildout.cfg I gave would trigger the installation of this egg 2) After installation of this egg, I would have mymodule.egg-link in the site-packages directory. But it seems that it's not at all the expected behavior ? Regards,
On Thu, Mar 18, 2010 at 2:05 PM, Saint Germain <saintger@gmail.com> wrote:
Hello,
I'm trying to use buildout with develop eggs, but it seems that they cannot be installed.
Here is the scenario :
1) 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
2) I use the following buildout.cfg [buildout] develop = /home/af79141/project parts = eggs
[eggs] recipe = zc.recipe.egg eggs = mymodule
3) I copy bootstrap.py in the directory (http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py)
4) python bootstrap.py
5) bin/buildout
I end up with the following content: bin bootstrap.py buildout.cfg develop-eggs eggs parts
No lib/python/site-packages are created !
Nor should they. When you use develop eggs, they are added to the develop-eggs directory.
But there is a file mymodule.egg-link in develop-eggs with the following content: /home/users/project
Yup, that's what you should get.
. What am I doing wrong ?
I don't know, what are you trying to do? Jim -- Jim Fulton
On Thu, 18 Mar 2010 15:23:10 -0400, Jim Fulton <jim@zope.com> wrote :
I'm trying to use buildout with develop eggs, but it seems that they cannot be installed.
I end up with the following content: bin bootstrap.py buildout.cfg develop-eggs eggs parts
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.
But there is a file mymodule.egg-link in develop-eggs with the following content: /home/users/project
Yup, that's what you should get.
. What am I doing wrong ?
I don't know, what are you trying to do?
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. What is the point to have the develop eggs in the develop-eggs if I'm not able to use them ? I was under the impression that I needed to install those eggs: http://www.k4ml.com/node/271 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 I hope that I was clear on my intent. Don't hesitate if it's not the case ! Regards,
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
participants (4)
-
Chris Withers -
Jim Fulton -
Mathieu Leduc-Hamel -
Saint Germain