o ThZ@s~ddlZddlmZddlmZmZmZmZmZm Z ddl m Z m Z ddl mZmZddlmZddlmZGd d d ZdS) N) ModuleType)AnyCallableDictListOptionalTuple)Lexiconhelpline) merge_dicts copy_dict)Context)Taskc@seZdZdZdededdfddZdJded eeddfd d Zdefd d Z de de fddZ de fddZ e    dKded eedeeeefdeedee ddf ddZ   dLddd eedeeedfdee ddf ddZ  dMd dd eedee ddfd!d"Zd eddfd#d$Zd%edeeeffd&d'Zd%eddfd(d)ZdJd eedefd*d+Zd ed,ed-eeefdeeeeefffd.d/Zd eedeeeeefffd0d1Zd ede fd2d3Z dJd4ee deefd5d6Zd7ed8edefd9d:Zd edefd;d<Z d=e!de!fd>d?Z"e#deeeeffd@dAZ$dJdBeedeeeffdCdDZ%dEeeefddfdFdGZ&deeeffdHdIZ'dS)N Collectionzg A collection of executable tasks. See :doc:`/concepts/namespaces`. .. versionadded:: 1.0 argskwargsreturnNcOst|_t|_d|_d|_i|_|dd|_|dd|_|jdur'd|_t |}|r=t |dt r=| |d|_|D]}| |q?|D] \}}| ||qKdS)a Create a new task collection/namespace. `.Collection` offers a set of methods for building a collection of tasks from scratch, plus a convenient constructor wrapping said API. In either case: * The first positional argument may be a string, which (if given) is used as the collection's default name when performing namespace lookups; * A ``loaded_from`` keyword argument may be given, which sets metadata indicating the filesystem path the collection was loaded from. This is used as a guide when loading per-project :ref:`configuration files `. * An ``auto_dash_names`` kwarg may be given, controlling whether task and collection names have underscores turned to dashes in most cases; it defaults to ``True`` but may be set to ``False`` to disable. The CLI machinery will pass in the value of the ``tasks.auto_dash_names`` config value to this kwarg. **The method approach** May initialize with no arguments and use methods (e.g. `.add_task`/`.add_collection`) to insert objects:: c = Collection() c.add_task(some_task) If an initial string argument is given, it is used as the default name for this collection, should it be inserted into another collection as a sub-namespace:: docs = Collection('docs') docs.add_task(doc_task) ns = Collection() ns.add_task(top_level_task) ns.add_collection(docs) # Valid identifiers are now 'top_level_task' and 'docs.doc_task' # (assuming the task objects were actually named the same as the # variables we're using :)) For details, see the API docs for the rest of the class. **The constructor approach** All ``*args`` given to `.Collection` (besides the abovementioned optional positional 'name' argument and ``loaded_from`` kwarg) are expected to be `.Task` or `.Collection` instances which will be passed to `.add_task`/`.add_collection` as appropriate. Module objects are also valid (as they are for `.add_collection`). For example, the below snippet results in the same two task identifiers as the one above:: ns = Collection(top_level_task, Collection('docs', doc_task)) If any ``**kwargs`` are given, the keywords are used as the initial name arguments for the respective values:: ns = Collection( top_level_task=some_other_task, docs=Collection(doc_task) ) That's exactly equivalent to:: docs = Collection(doc_task) ns = Collection() ns.add_task(some_other_task, 'top_level_task') ns.add_collection(docs, 'docs') See individual methods' API docs for details. N loaded_fromauto_dash_namesTr)r tasks collectionsdefaultname_configurationpoprrlist isinstancestr transform _add_objectitems)selfrr_argsargrobjr&D/var/www/html/venv/lib/python3.10/site-packages/invoke/collection.py__init__s"K  zCollection.__init__r%rcCsJt|tr |j}nt|ttfr|j}n tdt||||ddS)NzNo idea how to insert {!r}!r) rradd_taskrradd_collection TypeErrorformattype)r"r%rmethodr&r&r'r ts zCollection._add_objectcCsBt|j}dd|jD}d|jdt|t|S)NcSsg|]}d|qS)z{}...)r-.0xr&r&r' z'Collection.__repr__..zz, )rrkeysrr-rjoinsorted)r" task_namesrr&r&r'__repr__~s zCollection.__repr__othercCs2t|tr|j|jko|j|jko|j|jkSdS)NF)rrrrr)r"r:r&r&r'__eq__s    zCollection.__eq__cCs t|jSN)boolr8r"r&r&r'__bool__s zCollection.__bool__moduleconfigrrcsjddd dttddffdd }d D]B}t|d}|r_t|tr_||jd } | |j | _ | |j | _ |j rI| |j nd| _ t |j} |rXt| || | _| Sqtd d t} |} | D]} | | qp|r| || S)a# Return a new `.Collection` created from ``module``. Inspects ``module`` for any `.Task` instances and adds them to a new `.Collection`, returning it. If any explicit namespace collections exist (named ``ns`` or ``namespace``) a copy of that collection object is preferentially loaded instead. When the implicit/default collection is generated, it will be named after the module's ``__name__`` attribute, or its last dotted section if it's a submodule. (I.e. it should usually map to the actual ``.py`` filename.) Explicitly given collections will only be given that module-derived name if they don't already have a valid ``.name`` attribute. If the module has a docstring (``__doc__``) it is copied onto the resulting `.Collection` (and used for display in help, list etc output.) :param str name: A string, which if given will override any automatically derived collection name (or name set on the module's root namespace, if it has one.) :param dict config: Used to set config options on the newly created `.Collection` before returning it (saving you a call to `.configure`.) If the imported module had a root namespace object, ``config`` is merged on top of it (i.e. overriding any conflicts.) :param str loaded_from: Identical to the same-named kwarg from the regular class constructor - should be the path where the module was found. :param bool auto_dash_names: Identical to the same-named kwarg from the regular class constructor - determines whether emitted names are auto-dashed. .. versionadded:: 1.0 .Nobj_namerrcs4p|pg}td}|i|}j|_|S)N)rr)dict__doc__)rDrrinstancerclsrr@ module_namerr&r' instantiatesz+Collection.from_module..instantiate)ns namespace)rDcSs t|tSr<)rrr2r&r&r' z(Collection.from_module..r<)__name__splitrrgetattrrrr_transform_lexiconrrrrr rr filtervarsvaluesr* configure)rIr@rrArrrK candidater%ret obj_configr collectiontaskr&rHr' from_modules.4&      zCollection.from_moduler]raliases.rcCs|dur$|jr |j}nt|jdr|jj}nt|jdr |j}ntd||}||jvr7d}t||||j |<t |j t |pDgD] }|j j |||dqG|dus`|durj|j rl||||_dSdSdS)a Add `.Task` ``task`` to this collection. :param task: The `.Task` object to add to this collection. :param name: Optional string name to bind to (overrides the task's own self-defined ``name`` attribute and/or any Python identifier (i.e. ``.func_name``.) :param aliases: Optional iterable of additional names to bind the task as, on top of the primary name. These will be used in addition to any aliases the task itself declares internally. :param default: Whether this task should be the collection default. .. versionadded:: 1.0 N func_namerQz&Could not obtain a name for this task!zFName conflict: this collection has a sub-collection named {!r} already)toT)rhasattrbodyr`rQ ValueErrorrrr-rrr_alias is_default_check_default_collisionr)r"r]rr_rerrrer&r&r'r*s&        zCollection.add_taskcollcCsvt|tr t|}|p|j}|std||}||jvr(d}t||||j |<|r9| |||_ dSdS)a Add `.Collection` ``coll`` as a sub-collection of this one. :param coll: The `.Collection` to add. :param str name: The name to attach the collection as. Defaults to the collection's own internal name. :param default: Whether this sub-collection('s default task-or-collection) should be the default invocation of the parent collection. .. versionadded:: 1.0 .. versionchanged:: 1.5 Added the ``default`` parameter. z&Non-root collections must have a name!z`, up through the one actually holding the `.Task`. See `~.Collection.__getitem__` for semantics of the ``name`` argument. :returns: Two-tuple of (`.Task`, `dict`). .. versionadded:: 1.0 z$This collection has no default task.rB) configurationrrdrrnrtrr)r"rrsrirmr&r&r'rp|s  zCollection.task_with_configcCs$z||WdStyYdSw)NTF)KeyErrorrqr&r&r' __contains__s  zCollection.__contains__ignore_unknown_helpc Cs@g}|jD]\}}||}|t|||j|ddq|S)aw Returns all contained tasks and subtasks as a list of parser contexts. :param bool ignore_unknown_help: Passed on to each task's ``get_arguments()`` method. See the config option by the same name for details. .. versionadded:: 1.0 .. versionchanged:: 1.7 Added the ``ignore_unknown_help`` kwarg. )ry)rr_r)r8r!append ParserContext get_arguments)r"ryresultprimaryr_r]r&r&r' to_contextss zCollection.to_contextscollection_name task_namecCsd||||gS)NrB)r6r)r"rrr&r&r' subtask_nameszCollection.subtask_namecCs|s|Sd\}}|jsd\}}g}t|d}t|D]%\}}|d|fvr;||kr;||ddkr;||ddkr;|}||qd|S)a Transform ``name`` with the configured auto-dashes behavior. If the collection's ``auto_dash_names`` attribute is ``True`` (default), all non leading/trailing underscores are turned into dashes. (Leading/trailing underscores tend to get stripped elsewhere in the stack.) If it is ``False``, the inverse is applied - all dashes are turned into underscores. .. versionadded:: 1.0 )_-)rrr rrBru)rlen enumeraterzr6)r"rfrom_rareplacedendicharr&r&r'rs    zCollection.transformoldcCs^t}|D]\}}t||||<q|jD]\}}|j||||dq|S)zr Take a Lexicon and apply `.transform` to its keys and aliases. :returns: A new Lexicon. )rra)r r!copydeepcopyrr_re)r"rnewkeyvaluer&r&r'rTs zCollection._transform_lexiconcsi}jD]\}}ttj|j||<qjD],\}|jD]"\}}ttfdd|}|j|kr?|f7}|| |<q%q|S)a Return all task identifiers for this collection as a one-level dict. Specifically, a dict with the primary/"real" task names as the key, and any aliases as a list value. It basically collapses the namespace tree into a single easily-scannable collection of invocation strings, and is thus suitable for things like flat-style task listings or transformation into parser contexts. .. versionadded:: 1.0 cs |Sr<)rrN coll_namer"r&r'rOs z'Collection.task_names..) rr!rmaprr_rr8rr)r"rZrr]rirr_r&rr'r8s   zCollection.task_namestaskpathcCs |dur t|jS||dS)a Obtain merged configuration values from collection & children. :param taskpath: (Optional) Task name/path, identical to that used for `~.Collection.__getitem__` (e.g. may be dotted for nested tasks, etc.) Used to decide which path to follow in the collection tree when merging config values. :returns: A `dict` containing configuration values. .. versionadded:: 1.0 Nr )r rrp)r"rr&r&r'rv s zCollection.configurationoptionscCst|j|dS)a7 (Recursively) merge ``options`` into the current `.configuration`. Options configured this way will be available to all tasks. It is recommended to use unique keys to avoid potential clashes with other config options For example, if you were configuring a Sphinx docs build target directory, it's better to use a key like ``'sphinx.target'`` than simply ``'target'``. :param options: An object implementing the dictionary protocol. :returns: ``None``. .. versionadded:: 1.0 N)r r)r"rr&r&r'rX2szCollection.configurec sTjtjfddtjdddDddtjdddDdS) z Return an appropriate-for-serialization version of this object. See the documentation for `.Program` and its ``json`` task listing format; this method is the driver for that functionality. .. versionadded:: 1.0 cs4g|]}|jt|fdd|jDdqS)csg|]}|qSr&)r)r1yr>r&r'r3Vr4z4Collection.serialized...)rhelpr_)rrr r_r0r>r&r'r3Rs z)Collection.serialized..cSs|jSr<r)rNr&r&r'rOXsz'Collection.serialized..)rcSsg|]}|qSr&) serializedr0r&r&r'r3ZscSs |jpdS)Nrur)rNr&r&r'rO]rP)rrrrr)rr rr7rrWrr>r&r>r'rEs  zCollection.serializedr<)NNNN)NNN)NN)(rQ __module__ __qualname__rFrr(rrr r9objectr=r;r? classmethodrrr^rr*r+rgrnrorrrtrprxrr{rrrr rTpropertyr8rvrXrr&r&r&r'r sa   _ 2 )    $ ' r)rtypesrtypingrrrrrrutilr r rAr r parserrr{rrrr&r&r&r's