maas installs python modules with out any namespacing
Bug #1053507 reported by
Scott Moser
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
maas has essentially claimed the names 'provisioningse
Of those, only 'maasserver' makes even a bit of sense.
These should get namespaced into 'maas.apiclient', 'maas.provision
description: | updated |
Changed in maas: | |
importance: | Critical → High |
milestone: | none → 12.10 |
Changed in maas: | |
milestone: | 12.10 → 12.10-stabilization |
Changed in maas: | |
milestone: | none → 13.10 |
Changed in maas: | |
milestone: | 13.10 → 14.04 |
Changed in maas: | |
milestone: | 14.04 → 14.10 |
Changed in maas: | |
milestone: | 1.6.0 → none |
Changed in maas: | |
milestone: | none → next |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
We've wanted to address this for a long time, but there are some hurdles to overcome, and it's more work than it appears at first (we know this first hand). South completely lost its mind when we moved modules around, and Django wouldn't initialise for reasons we were never able to understand. However, renaming apiclient and provisioningserver will work okay.