Re: [Openstack-operators] Question on coding style on osops-tools-contrib repo

[Mike Dorman]

There is no standard strategy for this particular repo.  Although I do agree 
with you that the neutron directory is probably not the place for this.

I would suggest creating a top level lib/ directory and placing it there.  
There is already a multi/ directory, but that’s for scripts for non-specific 
services.  So I think it’s best to put library type things elsewhere.

Thanks!
Mike


On 12/21/16, 3:36 AM, "Saverio Proto"  wrote:

Hello,

in the osops-tools-contrib repo so far I proposed always python
scripts that are contained in a single file.

Now I have this file:
openstackapi.py

that I reuse in many scripts, look at this:
https://review.openstack.org/#/c/401409/

but maybe is not the best idea to commit this generic file in the
neutron folder.

any advice how to handle this ? what is the accepted python import strategy 
?

thanks

Saverio

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Question on coding style on osops-tools-contrib repo

[Saverio Proto]

Hello,

in the osops-tools-contrib repo so far I proposed always python
scripts that are contained in a single file.

Now I have this file:
openstackapi.py

that I reuse in many scripts, look at this:
https://review.openstack.org/#/c/401409/

but maybe is not the best idea to commit this generic file in the
neutron folder.

any advice how to handle this ? what is the accepted python import strategy ?

thanks

Saverio

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators