galaxy.tool_shed package¶
Subpackages¶
- galaxy.tool_shed.galaxy_install package
- Subpackages
- Submodules
- galaxy.tool_shed.galaxy_install.install_manager module
- galaxy.tool_shed.galaxy_install.installed_repository_manager module
- galaxy.tool_shed.galaxy_install.update_repository_manager module
- galaxy.tool_shed.metadata package
- galaxy.tool_shed.tools package
- galaxy.tool_shed.util package
- Submodules
- galaxy.tool_shed.util.basic_util module
- galaxy.tool_shed.util.container_util module
- galaxy.tool_shed.util.hg_util module
- galaxy.tool_shed.util.metadata_util module
- galaxy.tool_shed.util.repository_util module
- galaxy.tool_shed.util.shed_util_common module
- galaxy.tool_shed.util.tool_dependency_util module
- galaxy.tool_shed.util.tool_util module
Submodules¶
galaxy.tool_shed.repository_type module¶
galaxy.tool_shed.tool_shed_registry module¶
- class galaxy.tool_shed.tool_shed_registry.AUTH_TUPLE(username, password)[source]¶
Bases:
tuple- property username¶
Alias for field number 0
- property password¶
Alias for field number 1
- class galaxy.tool_shed.tool_shed_registry.Registry(config=None)[source]¶
Bases:
object- url_auth(url)[source]¶
If the tool shed is using external auth, the client to the tool shed must authenticate to that as well. This provides access to the six.moves.urllib.request.HTTPPasswordMgrWithdefaultRealm() object for the url passed in.
Following more what galaxy.demo_sequencer.controllers.common does might be more appropriate at some stage…