<feature>easier namespace designation using _modules</feature>
<feature>easier namespace designation using _modules</feature>

Developers can now designate namespaces by separating changing the
_modules list into a dictionary indexed by namespaces.  For example,

_modules = {'NamespaceOne': [ModuleOne, ModuleTwo, ModuleThree],
            'NamespaceTwo': [ModuleFour, ModuleFive]}

will assign ModuleOne, ModuleTwo, ModuleThree to the namespace
"NamespaceOne" and ModuleFour and ModuleFive to the namespace
"NamespaceTwo".  You may still use the tuple syntax in the modules
sublists so {'NamespaceThree': [(ModuleOne, {'abstract': True})]} will
work.  Also, if the namespace is redesignated in the module
dictionary, the redesignation takes precedence.

core/modules/module_registry:
  - ModuleRegistry.auto_add_module: remove unecessary line
  - ModuleRegistry.initialize: use package.module instead of
    package.init_module; add support for _modules being a dict and
    assign namespaces accordingly



hjanime/VisTrails,minesense/VisTrails,Nikea/VisTrails,hjanime/VisTrails,celiafish/VisTrails,Nikea/VisTrails,hjanime/VisTrails,minesense/VisTrails,Nikea/VisTrails,hjanime/VisTrails,minesense/VisTrails,hjanime/VisTrails,celiafish/VisTrails,Nikea/VisTrails,VisTrails/VisTrails,minesense/VisTrails,VisTrails/VisTrails,VisTrails/VisTrails,celiafish/VisTrails,VisTrails/VisTrails,VisTrails/VisTrails,celiafish/VisTrails,minesense/VisTrails