The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

description = "Start an IPython cluster for parallel computing.\n\nAn IPython cluster consists of 1 controller and 1 or more engines.\nThis command automates the startup of these processes using a wide\nrange of startup methods (SSH, local processes, PBS, mpiexec,\nWindows HPC Server 2008). To start a cluster with 4 engines on your\nlocal host simply do 'ipcluster start --n=4'. For more complex usage\nyou will typically do 'ipython profile create mycluster --parallel', then edit\nconfiguration files, followed by 'ipcluster start --profile=mycluster --n=4'.\n"¶

examples = '\nipcluster start --n=4 # start a 4 node cluster on localhost\nipcluster start -h # show the help string for the start subcmd\n\nipcluster stop -h # show the help string for the stop subcmd\nipcluster engines -h # show the help string for the engines subcmd\n'¶

Static handlers can be created by creating methods on a HasTraits
subclass with the naming convention ‘_[traitname]_changed’. Thus,
to create static handler for the trait ‘a’, create the method
_a_changed(self, name, old, new) (fewer arguments can be used, see
below).

Parameters :

handler : callable

A callable that is called when a trait changes. Its
signature can be handler(), handler(name), handler(name, new)
or handler(name, old, new).

name : list, str, None

If None, the handler will apply to all traits. If a list
of str, handler will apply to all names in the list. If a
str, the handler will apply just to that name.

remove : bool

If False (the default), then install the handler. If True
then unintall it.

subcommands = {'start': ('IPython.parallel.apps.ipclusterapp.IPClusterStart', "Start an IPython cluster for parallel computing\n\nStart an ipython cluster by its profile name or cluster\ndirectory. Cluster directories contain configuration, log and\nsecurity related files and are named using the convention\n'profile_<name>' and should be creating using the 'start'\nsubcommand of 'ipcluster'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster start --n=4 --profile=<profile>`,\notherwise use the 'profile-dir' option.\n"), 'stop': ('IPython.parallel.apps.ipclusterapp.IPClusterStop', "Stop a running IPython cluster\n\nStop a running ipython cluster by its profile name or cluster\ndirectory. Cluster directories are named using the convention\n'profile_<name>'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster stop --profile=<profile>`, otherwise\nuse the '--profile-dir' option.\n"), 'engines': ('IPython.parallel.apps.ipclusterapp.IPClusterEngines', "Start engines connected to an existing IPython cluster\n\nStart one or more engines to connect to an existing Cluster\nby profile name or cluster directory.\nCluster directories contain configuration, log and\nsecurity related files and are named using the convention\n'profile_<name>' and should be creating using the 'start'\nsubcommand of 'ipcluster'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster engines --n=4 --profile=<profile>`,\notherwise use the 'profile-dir' option.\n")}¶

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

description = "Start engines connected to an existing IPython cluster\n\nStart one or more engines to connect to an existing Cluster\nby profile name or cluster directory.\nCluster directories contain configuration, log and\nsecurity related files and are named using the convention\n'profile_<name>' and should be creating using the 'start'\nsubcommand of 'ipcluster'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster engines --n=4 --profile=<profile>`,\notherwise use the 'profile-dir' option.\n"¶

Static handlers can be created by creating methods on a HasTraits
subclass with the naming convention ‘_[traitname]_changed’. Thus,
to create static handler for the trait ‘a’, create the method
_a_changed(self, name, old, new) (fewer arguments can be used, see
below).

Parameters :

handler : callable

A callable that is called when a trait changes. Its
signature can be handler(), handler(name), handler(name, new)
or handler(name, old, new).

name : list, str, None

If None, the handler will apply to all traits. If a list
of str, handler will apply to all names in the list. If a
str, the handler will apply just to that name.

remove : bool

If False (the default), then install the handler. If True
then unintall it.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

description = "Start an IPython cluster for parallel computing\n\nStart an ipython cluster by its profile name or cluster\ndirectory. Cluster directories contain configuration, log and\nsecurity related files and are named using the convention\n'profile_<name>' and should be creating using the 'start'\nsubcommand of 'ipcluster'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster start --n=4 --profile=<profile>`,\notherwise use the 'profile-dir' option.\n"¶

Static handlers can be created by creating methods on a HasTraits
subclass with the naming convention ‘_[traitname]_changed’. Thus,
to create static handler for the trait ‘a’, create the method
_a_changed(self, name, old, new) (fewer arguments can be used, see
below).

Parameters :

handler : callable

A callable that is called when a trait changes. Its
signature can be handler(), handler(name), handler(name, new)
or handler(name, old, new).

name : list, str, None

If None, the handler will apply to all traits. If a list
of str, handler will apply to all names in the list. If a
str, the handler will apply just to that name.

remove : bool

If False (the default), then install the handler. If True
then unintall it.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.

description = "Stop a running IPython cluster\n\nStop a running ipython cluster by its profile name or cluster\ndirectory. Cluster directories are named using the convention\n'profile_<name>'. If your cluster directory is in\nthe cwd or the ipython directory, you can simply refer to it\nusing its profile name, 'ipcluster stop --profile=<profile>`, otherwise\nuse the '--profile-dir' option.\n"¶

Static handlers can be created by creating methods on a HasTraits
subclass with the naming convention ‘_[traitname]_changed’. Thus,
to create static handler for the trait ‘a’, create the method
_a_changed(self, name, old, new) (fewer arguments can be used, see
below).

Parameters :

handler : callable

A callable that is called when a trait changes. Its
signature can be handler(), handler(name), handler(name, new)
or handler(name, old, new).

name : list, str, None

If None, the handler will apply to all traits. If a list
of str, handler will apply to all names in the list. If a
str, the handler will apply just to that name.

remove : bool

If False (the default), then install the handler. If True
then unintall it.

The TraitTypes returned don’t know anything about the values
that the various HasTrait’s instances are holding.

This follows the same algorithm as traits does and does not allow
for any simple way of specifying merely that a metadata name
exists, but has any value. This is because get_metadata returns
None if a metadata key doesn’t exist.