editables with virtualenv are always put in develop-eggs-directory

saintgermain avatarsaintgermain created an issue

It seems that we should mirror the pip behavior here and let the *.egg-link in the site-packages directory instead of moving them in the develop-eggs-directory. I proposed a patch in the patch queue to solve the issue

Comments (2)

  1. Gael Pasgrimaud
    • changed status to open

    As I remember I do that so buildout can find them. eg: if you use zc.recipe.egg after the pip's recipe without this this buildout will try to reinstall them. May be we can copy egg-link instead of moving ?

  2. saintgermain

    Do you mean that you want to cover the case where we specified the same 'project' under the gp.recipe.pip and the zc.recipe.egg ? Because for regular (i.e. non-develop) project, you don't make a copy in the eggs directory, so buildout reinstall them again with zc.recipe.egg.

    If we suppose that gp.recipe.pip and zc.recipe.egg don't mess with one another, I don't see the problem of letting the eggs and develop-eggs untouched. If you want to install the same project with gp.recipe.pip and zc.recipe.egg, then you are free to do it (but yes it will be reinstall and you will have to be extra-careful for version conflict).

  3. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.