PBR Ignores git://, git+ssh://, git+https:// Requirement Lines
Bug #1467683 reported by
Ryan Bourgeois
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBR |
Fix Released
|
Wishlist
|
Sachi King |
Bug Description
PBR does not extract package names for requirements which begin with git://, git+ssh://, git+https:// unless they have the -e flag set. Pip is capable of handling these URL's without -e. However, with PBR omitting the -e causes the following setuptools error:
error in setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers
Some debugging indicates that the full line is being used instead of the package atom.
Changed in pbr: | |
assignee: | nobody → Ryan Bourgeois (bluedragonx) |
Changed in pbr: | |
status: | New → In Progress |
Changed in pbr: | |
status: | Confirmed → In Progress |
Changed in pbr: | |
assignee: | Ryan Bourgeois (bluedragonx) → Sachi King (nakato) |
Changed in pbr: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Are you sure its the -e, and not the presence/absence of an egg name? Anyhow, assuming you're right, then yes, we should fix this - though the direction with pbr is to move to consolidating on PEP-426 expressions. We probably have some work to do to teach setuptools about that and the related URL glue stuff.