tool_shed package

Subpackages

Submodules

tool_shed.repository_registry module

class tool_shed.repository_registry.Registry(app)[source]

Bases: object

__init__(app)[source]
add_category_entry(category)[source]
add_entry(repository)[source]
edit_category_entry(old_name, new_name)[source]
get_certified_level_one_clause_list()[source]
get_certified_level_one_tuple(repository)[source]

Return True if the latest installable changeset_revision of the received repository is level one certified.

is_level_one_certified(repository_metadata)[source]
is_valid(repository)[source]
load_certified_level_one_repository_and_suite_tuple(repository)[source]
load_repository_and_suite_tuple(repository)[source]
load_repository_and_suite_tuples()[source]
load_viewable_repositories_and_suites_by_category()[source]
remove_category_entry(category)[source]
remove_entry(repository)[source]
sa_session
unload_certified_level_one_repository_and_suite_tuple(repository)[source]
unload_repository_and_suite_tuple(repository)[source]

tool_shed.tool_shed_registry module

class tool_shed.tool_shed_registry.Registry(root_dir=None, config=None)[source]

Bases: object

__init__(root_dir=None, config=None)[source]
password_manager_for_url(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...

url_auth(url)[source]