Our setup.py needs to be a real setup.py
Bug #897943 reported by
Brad Hall
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Brad Hall |
Bug Description
Our setup.py is causing issues for other projects because it looks like a duck but doesn't quack like one. (i.e. we don't support all of the commands that a normal setup.py does):
https:/
Given that the distros will be doing the packaging we can just make one that that will encompass all the sub-packages until the client library is split out.
description: | updated |
Changed in quantum: | |
milestone: | none → essex-2 |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Brad Hall (bgh) |
Changed in quantum: | |
status: | Confirmed → In Progress |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
Horizon found a way to work around this, so its no longer as high priority, so we're bumping to E-3