[jira] [Commented] (CLOUDSTACK-414) marvin cloudstackAPI is packaging each api call in its separate module, we should create a single module

["Rohit Yadav (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490194#comment-13490194 ] 

Rohit Yadav commented on CLOUDSTACK-414:
----------------------------------------

One can simply put import *, or from x import y (see cloudstack api client module example) 
But, what exactly is the issue? Every module has a Cmd and Response classes along with helper classes; putting all of them in one module will them hard to hack, slow imports and runtime overheads. To inspect one can get __all__ from cloudstackAPI, (note that every module has a moduleCmd, moduleResponse class) one can use dir, getattr, setattr to work on them.
                
> marvin cloudstackAPI is packaging each api call in its separate module, we should create a single module
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-414
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-414
>             Project: CloudStack
>          Issue Type: Improvement
>          Components: API, Test Tools
>    Affects Versions: 4.1.0
>         Environment: Devcloud, OSX 10.8.1
>            Reporter: sebastien goasguen
>            Priority: Critical
>
> build-marvin uses codegenerator.py to create the cloudstackAPI/ in the marvin tree. The way this is done each API is its own module. This makes it troublesome to use the cloudstackAPI in python. We may want to create a single cloudstackapi file which contains all the skeleton classes generated.
> That way something like inspect.getmembers(cloudstackAPI,inspect.isclass) will return something.

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