incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noa Resare (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-964) fix python module naming
Date Sat, 12 Jan 2013 09:42:12 GMT
Noa Resare created CLOUDSTACK-964:
-------------------------------------

             Summary: 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

Mime
View raw message