swift-init uses fixed path to Python interpreter, breaking virtualenv
Bug #737979 reported by
Ewan Mellor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Low
|
Ewan Mellor | ||
| OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
glance-control uses #!/usr/bin/python, not #!/usr/bin/env python. This breaks virtualenv, which means that tests.unit.
This also applies to swift-init.
This bug has now been fixed for glance-control, but not for swift-init.
Related branches
lp:~ewanmellor/glance/lp737979
- Jay Pipes (community): Approve
- Todd Willey (community): Approve
-
Diff: 9 lines (+1/-1)1 file modifiedbin/glance-control (+1/-1)
| Changed in glance: | |
| assignee: | nobody → Ewan Mellor (ewanmellor) |
| status: | New → In Progress |
Revision history for this message
| Jay Pipes (jaypipes) wrote | #1 |
| Changed in glance: | |
| importance: | Undecided → Low |
| milestone: | none → cactus-2011-03-24 |
| Changed in swift: | |
| importance: | Undecided → Low |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| milestone: | cactus-2011-03-24 → 2011.2 |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Ewan Mellor (ewanmellor) wrote | #2 |
| summary: |
- glance-control uses fixed path to Python interpreter, breaking - virtualenv + swift-init uses fixed path to Python interpreter, breaking virtualenv |
| description: | updated |
| Changed in swift: | |
| status: | New → Fix Released |
To post a comment you must log in.
Note to Swifties:
This came up because I actually use glance-control (which is a slightly modified copy of swift-init) in my functional tests, which for Glance, can be run in a virtualenv with ./run_tests.sh -V.
Anyway, it's a simple fix, as you can see. Checked, and swift-init still hard-codes Python interpreter location.