cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-964) fix python module naming
Date Wed, 08 Feb 2017 09:24:00 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daan Hoogland closed CLOUDSTACK-964.
------------------------------------
    Resolution: Won't Fix

> 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 was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message