entry-points are not found for develop-eggs
Bug #662114 reported by
Devin Bayer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
New
|
Undecided
|
Unassigned |
Bug Description
the bug
---------
I define entry-points for the egg I'm developing in setup.py. Take this example:
When I run zc.recipe.egg or z3c.recipe.scripts without an eggs option, nothing happens.
When I add the options "egg = myegg", an old version of myegg is installed in eggs/ and the old entry-points are used.
workaround
--------------
Adding an explicit entry-points setting works, but I need to duplicate setup.py. I wish this was documented, as it's not clear how the develop and eggs options interact.
suggested fix
----------------
Add a "develop-egg" setting which works like "develop", but runs "setup.py develop" and reads "*.egg_info" directories to find entry points.
To post a comment you must log in.