You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2013/01/12 11:38:12 UTC
[jira] [Commented] (CLOUDSTACK-964) fix python module naming
[ https://issues.apache.org/jira/browse/CLOUDSTACK-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551879#comment-13551879 ]
Rohit Yadav commented on CLOUDSTACK-964:
----------------------------------------
For this we've marvin, we should move out any useful code to tools/marvin and delete cloud-cli and python both of them are old and are longer maintained.
> fix python module naming
> ------------------------
>
> Key: CLOUDSTACK-964
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-964
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Noa Resare
> Priority: Minor
>
> There are two toplevel python modules that is part of cloudstack, named 'coud_utils' and 'cloudutils' respectively. This seems very much like an artifact of the development of the project rather than actual design.
> I propose we make things a bit more straightforward by putting all modules into a single namespace with a name easily derived from the project name, such as 'cloudstack', and update import statements accordingly.
> So, is this an incompatible change to a published API or not? I would claim it is not, and the fact that the python modules gets installed into the system python path by default is just a side effect of people doing packaging not being up to date on how private python packaging is normally done in Debian.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira