Extension names for packages discovered by path are unintuitive.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
Undecided
|
David Scannell |
Bug Description
This is a minor issues for extensions. I've attached a super-simple patch that will tweak the names for extensions discovered by path. Below is the comment on the patch that explains it.
-- patch message --
Using novaclient with some extensions via python code, you might have an
invocation like this:
extensions = shell.OpenStack
novaclient = Client("1.1", user, apikey, project, authurl, extensions=
If you have an extension like 'myextension.py' in the v1_1/contrib directory, you'll
end up with a very sensible attribute on the resulting novaclient object, i.e.
novaclient.
If you have a package distributed in the package myextension_
then it'll automatically be picked up as an extension (awesome!) but the name is not
as intuitive.
novaclient
This patch simply changes this to use the Extension 'name' of myextension, even when
matching extensions found in packages. The possibility of collisions exists, but is
not really any more significant than before (where you might have different versions
of the same package installed in the system or heck, even a bizarrely named
'myextension_
security vulnerability: | no → yes |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
Sorry about that, I'm not familiar with the launchpad interface I accidentally changed the information type. Doesn't look like it'll open a menu (no cursor change, etc.).