Description
If I:
- cd myapp
- python setup.py sdist
- pip bundle myapp.bundle dist/myapp*tar.gz
(I do this as part of a multi-facted packing and distribution thing. Some people want/get eggs off PyPI, some get tarballs, some get bundles, etc, so building the bundles from the tarballs is sort of useful, if there's a more direct way, do tell me, but I still perceive what I'm describing to be a bug.)
The resulting bundle includes all the requirements for my app, but not my app. I've traced this down to being caused by the top level package (myapp) being added as an unnamed requirement (in RequirmentSet.add_requirement()) because InstallRequirement.from_line() doesn't produce a name in this case. unamed requirements seem not to be handled.
Should it? I dug around in the code to see if I could up with a way to make do that and found myself in a maze of twisty passages, so thought I'd report the bug and get some coffee, stew a bit.
Thanks!
- Bitbucket: https://bitbucket.org/ianb/pip/issue/38
- Originally Reported By:
- Originally Created At: 2009-12-10 11:02:16