Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Ryan Brown
On 10/06/2015 05:15 PM, Thomas Goirand wrote: Hi, tl;dr: let's add a exception handling so that python-*client having conflicting command names isn't a problem anymore, and "openstack help" always work as much as it can. Standardizing on "openstack verb" would likely be the best

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Hayes, Graham
On 07/10/15 14:42, Ryan Brown wrote: > On 10/06/2015 05:15 PM, Thomas Goirand wrote: >> Hi, >> >> tl;dr: let's add a exception handling so that python-*client having >> conflicting command names isn't a problem anymore, and "openstack help" >> always work as much as it can. > > Standardizing on

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Thomas Goirand
On 10/07/2015 03:57 PM, Hayes, Graham wrote: > On 07/10/15 14:42, Ryan Brown wrote: >> On 10/06/2015 05:15 PM, Thomas Goirand wrote: >>> P.S: It wasn't the point of this message, but do we have a fix for >>> designateclient? It'd be nice to have this fixed before Liberty is out. > > Is there a

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Dean Troyer
On Wed, Oct 7, 2015 at 8:39 AM, Ryan Brown wrote: > Standardizing on "openstack verb" would likely be the > best solution for both the immediate problem and for the broader "naming > stuff" issue. > This is the approach that a number of plugins are taking. I have

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Thomas Goirand
On 10/07/2015 03:39 PM, Ryan Brown wrote: > Sharing a flat namespace is a recipe for pain with a growing number of > projects. Devs and users are unlikely to use every project, they > probably won't notice conflicts naturally except in cases like horizon. Well, users would typically install

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Dean Troyer
On Tue, Oct 6, 2015 at 4:15 PM, Thomas Goirand wrote: > tl;dr: let's add a exception handling so that python-*client having > conflicting command names isn't a problem anymore, and "openstack help" > always work as much as it can. > This creates a first-one-wins scenario that

Re: [openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-07 Thread Sean Dague
On 10/07/2015 10:50 AM, Dean Troyer wrote: > On Wed, Oct 7, 2015 at 8:39 AM, Ryan Brown > wrote: > > Standardizing on "openstack verb" would likely > be the best solution for both the immediate problem and for the > broader

[openstack-dev] conflicting names in python-openstackclient: could we have some exception handling please?

2015-10-06 Thread Thomas Goirand
Hi, tl;dr: let's add a exception handling so that python-*client having conflicting command names isn't a problem anymore, and "openstack help" always work as much as it can. Longer version: This is just a suggestion for contributors to python-openstackclient. I saw a few packages that had