flower-hierarchy 2.2.0.1__tar.gz

flower_hierarchy-2.2.0.1/LICENSE

@@ -0,0 +1,28 @@
+Copyright (c) 2012, Mher Movsisyan and individual contributors.
+All rights reserved. 
+
+Redistribution and use in source and binary forms, with or without 
+modification, are permitted provided that the following conditions are met: 
+
+ * Redistributions of source code must retain the above copyright notice, 
+   this list of conditions and the following disclaimer. 
+
+ * Redistributions in binary form must reproduce the above copyright 
+   notice, this list of conditions and the following disclaimer in the 
+   documentation and/or other materials provided with the distribution. 
+
+ * Neither the name of the Celery Flower nor the names of its contributors 
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission. 
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE 
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
+POSSIBILITY OF SUCH DAMAGE.

flower_hierarchy-2.2.0.1/MANIFEST.in

@@ -0,0 +1,10 @@
+include AUTHORS
+include CHANGES
+include LICENSE
+include MANIFEST.in
+include README.rst
+recursive-include docs *
+recursive-include flower/static *
+recursive-include flower/templates *
+recursive-include tests *
+recursive-include requirements *.txt

flower_hierarchy-2.2.0.1/PKG-INFO

@@ -0,0 +1,227 @@
+Metadata-Version: 2.4
+Name: flower-hierarchy
+Version: 2.2.0.1
+Summary: Celery Flower with tasks shown under the task that started them
+Home-page: https://github.com/salvamunoz/flower_hierarchy
+Author: Mher Movsisyan
+Maintainer: Salvador Muñoz
+Maintainer-email: salva17y2@gmail.com
+License: BSD
+Project-URL: Source, https://github.com/salvamunoz/flower_hierarchy
+Project-URL: Issues, https://github.com/salvamunoz/flower_hierarchy/issues
+Project-URL: Upstream, https://github.com/mher/flower
+Project-URL: Documentation, https://flower.readthedocs.io
+Keywords: celery,flower,monitoring,task hierarchy,workflow
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: BSD License
+Classifier: Topic :: System :: Distributed Computing
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: celery>=5.0.5
+Requires-Dist: tornado<7.0.0,>=6.5.7
+Requires-Dist: prometheus_client>=0.8.0
+Requires-Dist: humanize
+Requires-Dist: pytz
+Dynamic: author
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: keywords
+Dynamic: license
+Dynamic: license-file
+Dynamic: maintainer
+Dynamic: maintainer-email
+Dynamic: project-url
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+flower-hierarchy
+================
+
+.. image:: https://img.shields.io/pypi/v/flower-hierarchy.svg
+    :target: https://pypi.org/project/flower-hierarchy/
+    :alt: PyPI
+.. image:: https://github.com/salvamunoz/flower_hierarchy/workflows/Build/badge.svg
+    :target: https://github.com/salvamunoz/flower_hierarchy/actions
+    :alt: Build
+
+A fork of `Flower <https://github.com/mher/flower>`_, the web application for
+monitoring and managing Celery clusters, that shows each task under the task
+that started it.
+
+Flower lists tasks one after the other. In flower-hierarchy, the tasks a task
+sends with ``delay``/``apply_async``, the steps of a chain, groups and chords
+appear below it as a tree you can expand and collapse, with a summary of what
+happened below each task::
+
+    ▼ process_order        SUCCESS   3 below
+        ├─ validate_order  SUCCESS
+        ├─ charge_card     SUCCESS
+        └─ send_email      SUCCESS
+    ▼ import_data          SUCCESS   3 below · 1 failed
+        └─ download        SUCCESS
+            └─ parse       SUCCESS
+                └─ persist FAILURE
+
+.. image:: https://raw.githubusercontent.com/salvamunoz/flower_hierarchy/master/docs/screenshots/task-hierarchy.png
+    :alt: The tasks page with a chain of tasks expanded
+
+Everything else works as in Flower: same command, options, API and Docker
+usage.
+
+What's different from Flower
+----------------------------
+
+- **Tree layout of the tasks page**, recursive to any depth, built from the
+  ``parent_id`` that Celery puts in its events. No extra setup on the workers
+  and any broker works.
+- **Expand all levels** of a task at once: the double chevron next to it,
+  Alt+click or Shift+click on its toggle, or ``*`` on the keyboard.
+- **Subtree summaries**: a task shows how many tasks are below it and how many
+  failed or are still running, so a failure deep in a workflow is visible from
+  the top.
+- **Search keeps the context**: matching tasks are listed under their
+  top-level task, with the tasks leading to them dimmed.
+- **Live** button that reloads the table every few seconds, and **Tree** /
+  **Flat** buttons to switch to Flower's list.
+- ``GET /api/task/tree/<task-id>``: a task and its descendants as nested JSON.
+- Retries and ``Task.replace`` no longer make a task its own child.
+
+See `Task hierarchy <https://github.com/salvamunoz/flower_hierarchy/blob/master/docs/task_hierarchy.rst>`_
+for how relations are found, what Celery's events can't tell (for instance
+groups sent from outside a task) and the limits on large trees.
+
+Features
+--------
+
+.. features-start
+
+- Real-time monitoring using Celery Events
+    - View task progress and history
+    - View tasks under the task that started them, as an expandable tree
+    - View task details (arguments, start time, runtime, and more)
+- Remote Control
+    - View worker status and statistics
+    - Shutdown and restart worker instances
+    - Control worker pool size and autoscale settings
+    - View and modify the queues a worker instance consumes from
+    - View currently running tasks
+    - View scheduled tasks (ETA/countdown)
+    - View reserved and revoked tasks
+    - Apply time and rate limits
+    - Revoke or terminate tasks
+- Broker monitoring
+    - View statistics for all Celery queues
+- HTTP Basic Auth, Google, Github, Gitlab and Okta OAuth
+- Prometheus integration
+- API
+
+.. features-end
+
+.. install-start
+
+Installation
+------------
+
+flower-hierarchy replaces Flower: both provide the ``flower`` Python package,
+so remove Flower first if it is installed ::
+
+    $ pip uninstall flower
+    $ pip install flower-hierarchy
+
+The development version can be installed from GitHub ::
+
+    $ pip install git+https://github.com/salvamunoz/flower_hierarchy.git
+
+In a requirements file, list ``flower-hierarchy`` instead of ``flower``.
+
+Usage
+-----
+
+flower-hierarchy is started like Flower. Provide the broker URL ::
+
+    $ celery --broker=amqp://guest:guest@localhost:5672// flower
+
+Or use the configuration of your `celery application <https://docs.celeryq.dev/en/stable/userguide/application.html>`_ ::
+
+    $ celery -A tasks.app flower
+
+Workers must send task events, with ``-E`` or ``worker_send_task_events = True``.
+
+By default, flower runs on port 5555, which can be modified with the `port <https://flower.readthedocs.io/en/latest/config.html#port>`_ option ::
+
+    $ celery -A tasks.app flower --port=5001
+
+The tasks page opens in the tree layout. ``/tasks?view=flat`` opens Flower's
+list, and ``/tasks?autorefresh=5`` turns on Live with a 5 second interval.
+
+Docker
+------
+
+Build the image from this repository ::
+
+    $ docker build -t flower-hierarchy https://github.com/salvamunoz/flower_hierarchy.git
+    $ docker run -v $(pwd)/examples:/data -p 5555:5555 flower-hierarchy celery --app=tasks.app flower
+
+In this example, Flower is using the `tasks.app` defined in the `examples/tasks.py <https://github.com/salvamunoz/flower_hierarchy/blob/master/examples/tasks.py>`_ file
+
+.. install-end
+
+Versions
+--------
+
+Versions are the Flower release the fork is based on, followed by the fork's
+own release number: ``2.2.0.1`` is the first release on top of Flower 2.2.0.
+
+API
+---
+
+The Flower API lets you manage the cluster over HTTP.
+
+For example you can grow a worker's pool by: ::
+
+    $ curl -X POST -d 'n=1' http://localhost:5555/api/worker/pool/grow/celery@$(hostname)
+
+Or call a task by: ::
+
+    $ curl -X POST -d '{"args":[1,2]}' http://localhost:5555/api/task/async-apply/tasks.add
+
+Or get a task and everything it started by: ::
+
+    $ curl http://localhost:5555/api/task/tree/8a4da87b-e12b-4547-b89a-e92e4d1f8efd
+
+For more info, see Flower's `API Reference`_
+
+.. _API Reference: https://flower.readthedocs.io/en/latest/api.html
+
+Documentation
+-------------
+
+Flower's documentation applies to flower-hierarchy, see `Read the Docs`_.
+The tree layout is described in `docs/task_hierarchy.rst <https://github.com/salvamunoz/flower_hierarchy/blob/master/docs/task_hierarchy.rst>`_.
+
+.. _Read the Docs: https://flower.readthedocs.io
+
+Credits and license
+-------------------
+
+flower-hierarchy is based on `Flower <https://github.com/mher/flower>`_ by
+Mher Movsisyan and its contributors, and keeps its BSD 3-Clause License.
+See the `License`_ file for the full license text.
+
+.. _`License`: https://github.com/salvamunoz/flower_hierarchy/blob/master/LICENSE

flower_hierarchy-2.2.0.1/README.rst

@@ -0,0 +1,175 @@
+flower-hierarchy
+================
+
+.. image:: https://img.shields.io/pypi/v/flower-hierarchy.svg
+    :target: https://pypi.org/project/flower-hierarchy/
+    :alt: PyPI
+.. image:: https://github.com/salvamunoz/flower_hierarchy/workflows/Build/badge.svg
+    :target: https://github.com/salvamunoz/flower_hierarchy/actions
+    :alt: Build
+
+A fork of `Flower <https://github.com/mher/flower>`_, the web application for
+monitoring and managing Celery clusters, that shows each task under the task
+that started it.
+
+Flower lists tasks one after the other. In flower-hierarchy, the tasks a task
+sends with ``delay``/``apply_async``, the steps of a chain, groups and chords
+appear below it as a tree you can expand and collapse, with a summary of what
+happened below each task::
+
+    ▼ process_order        SUCCESS   3 below
+        ├─ validate_order  SUCCESS
+        ├─ charge_card     SUCCESS
+        └─ send_email      SUCCESS
+    ▼ import_data          SUCCESS   3 below · 1 failed
+        └─ download        SUCCESS
+            └─ parse       SUCCESS
+                └─ persist FAILURE
+
+.. image:: https://raw.githubusercontent.com/salvamunoz/flower_hierarchy/master/docs/screenshots/task-hierarchy.png
+    :alt: The tasks page with a chain of tasks expanded
+
+Everything else works as in Flower: same command, options, API and Docker
+usage.
+
+What's different from Flower
+----------------------------
+
+- **Tree layout of the tasks page**, recursive to any depth, built from the
+  ``parent_id`` that Celery puts in its events. No extra setup on the workers
+  and any broker works.
+- **Expand all levels** of a task at once: the double chevron next to it,
+  Alt+click or Shift+click on its toggle, or ``*`` on the keyboard.
+- **Subtree summaries**: a task shows how many tasks are below it and how many
+  failed or are still running, so a failure deep in a workflow is visible from
+  the top.
+- **Search keeps the context**: matching tasks are listed under their
+  top-level task, with the tasks leading to them dimmed.
+- **Live** button that reloads the table every few seconds, and **Tree** /
+  **Flat** buttons to switch to Flower's list.
+- ``GET /api/task/tree/<task-id>``: a task and its descendants as nested JSON.
+- Retries and ``Task.replace`` no longer make a task its own child.
+
+See `Task hierarchy <https://github.com/salvamunoz/flower_hierarchy/blob/master/docs/task_hierarchy.rst>`_
+for how relations are found, what Celery's events can't tell (for instance
+groups sent from outside a task) and the limits on large trees.
+
+Features
+--------
+
+.. features-start
+
+- Real-time monitoring using Celery Events
+    - View task progress and history
+    - View tasks under the task that started them, as an expandable tree
+    - View task details (arguments, start time, runtime, and more)
+- Remote Control
+    - View worker status and statistics
+    - Shutdown and restart worker instances
+    - Control worker pool size and autoscale settings
+    - View and modify the queues a worker instance consumes from
+    - View currently running tasks
+    - View scheduled tasks (ETA/countdown)
+    - View reserved and revoked tasks
+    - Apply time and rate limits
+    - Revoke or terminate tasks
+- Broker monitoring
+    - View statistics for all Celery queues
+- HTTP Basic Auth, Google, Github, Gitlab and Okta OAuth
+- Prometheus integration
+- API
+
+.. features-end
+
+.. install-start
+
+Installation
+------------
+
+flower-hierarchy replaces Flower: both provide the ``flower`` Python package,
+so remove Flower first if it is installed ::
+
+    $ pip uninstall flower
+    $ pip install flower-hierarchy
+
+The development version can be installed from GitHub ::
+
+    $ pip install git+https://github.com/salvamunoz/flower_hierarchy.git
+
+In a requirements file, list ``flower-hierarchy`` instead of ``flower``.
+
+Usage
+-----
+
+flower-hierarchy is started like Flower. Provide the broker URL ::
+
+    $ celery --broker=amqp://guest:guest@localhost:5672// flower
+
+Or use the configuration of your `celery application <https://docs.celeryq.dev/en/stable/userguide/application.html>`_ ::
+
+    $ celery -A tasks.app flower
+
+Workers must send task events, with ``-E`` or ``worker_send_task_events = True``.
+
+By default, flower runs on port 5555, which can be modified with the `port <https://flower.readthedocs.io/en/latest/config.html#port>`_ option ::
+
+    $ celery -A tasks.app flower --port=5001
+
+The tasks page opens in the tree layout. ``/tasks?view=flat`` opens Flower's
+list, and ``/tasks?autorefresh=5`` turns on Live with a 5 second interval.
+
+Docker
+------
+
+Build the image from this repository ::
+
+    $ docker build -t flower-hierarchy https://github.com/salvamunoz/flower_hierarchy.git
+    $ docker run -v $(pwd)/examples:/data -p 5555:5555 flower-hierarchy celery --app=tasks.app flower
+
+In this example, Flower is using the `tasks.app` defined in the `examples/tasks.py <https://github.com/salvamunoz/flower_hierarchy/blob/master/examples/tasks.py>`_ file
+
+.. install-end
+
+Versions
+--------
+
+Versions are the Flower release the fork is based on, followed by the fork's
+own release number: ``2.2.0.1`` is the first release on top of Flower 2.2.0.
+
+API
+---
+
+The Flower API lets you manage the cluster over HTTP.
+
+For example you can grow a worker's pool by: ::
+
+    $ curl -X POST -d 'n=1' http://localhost:5555/api/worker/pool/grow/celery@$(hostname)
+
+Or call a task by: ::
+
+    $ curl -X POST -d '{"args":[1,2]}' http://localhost:5555/api/task/async-apply/tasks.add
+
+Or get a task and everything it started by: ::
+
+    $ curl http://localhost:5555/api/task/tree/8a4da87b-e12b-4547-b89a-e92e4d1f8efd
+
+For more info, see Flower's `API Reference`_
+
+.. _API Reference: https://flower.readthedocs.io/en/latest/api.html
+
+Documentation
+-------------
+
+Flower's documentation applies to flower-hierarchy, see `Read the Docs`_.
+The tree layout is described in `docs/task_hierarchy.rst <https://github.com/salvamunoz/flower_hierarchy/blob/master/docs/task_hierarchy.rst>`_.
+
+.. _Read the Docs: https://flower.readthedocs.io
+
+Credits and license
+-------------------
+
+flower-hierarchy is based on `Flower <https://github.com/mher/flower>`_ by
+Mher Movsisyan and its contributors, and keeps its BSD 3-Clause License.
+See the `License`_ file for the full license text.
+
+.. _`License`: https://github.com/salvamunoz/flower_hierarchy/blob/master/LICENSE

flower_hierarchy-2.2.0.1/docs/Makefile

@@ -0,0 +1,177 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+PAPER         =
+BUILDDIR      = .build
+
+# User-friendly check for sphinx-build
+ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
+$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
+endif
+
+# Internal variables.
+PAPEROPT_a4     = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+# the i18n builder cannot share the environment and doctrees with the others
+I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
+
+help:
+	@echo "Please use \`make <target>' where <target> is one of"
+	@echo "  html       to make standalone HTML files"
+	@echo "  dirhtml    to make HTML files named index.html in directories"
+	@echo "  singlehtml to make a single large HTML file"
+	@echo "  pickle     to make pickle files"
+	@echo "  json       to make JSON files"
+	@echo "  htmlhelp   to make HTML files and a HTML help project"
+	@echo "  qthelp     to make HTML files and a qthelp project"
+	@echo "  devhelp    to make HTML files and a Devhelp project"
+	@echo "  epub       to make an epub"
+	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
+	@echo "  latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
+	@echo "  text       to make text files"
+	@echo "  man        to make manual pages"
+	@echo "  texinfo    to make Texinfo files"
+	@echo "  info       to make Texinfo files and run them through makeinfo"
+	@echo "  gettext    to make PO message catalogs"
+	@echo "  changes    to make an overview of all changed/added/deprecated items"
+	@echo "  xml        to make Docutils-native XML files"
+	@echo "  pseudoxml  to make pseudoxml-XML files for display purposes"
+	@echo "  linkcheck  to check all external links for integrity"
+	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
+
+clean:
+	rm -rf $(BUILDDIR)/*
+
+html:
+	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
+
+dirhtml:
+	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
+
+singlehtml:
+	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
+	@echo
+	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
+
+pickle:
+	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
+	@echo
+	@echo "Build finished; now you can process the pickle files."
+
+json:
+	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+	@echo
+	@echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
+	@echo
+	@echo "Build finished; now you can run HTML Help Workshop with the" \
+	      ".hhp project file in $(BUILDDIR)/htmlhelp."
+
+qthelp:
+	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
+	@echo
+	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
+	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/flower.qhcp"
+	@echo "To view the help file:"
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/flower.qhc"
+
+devhelp:
+	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
+	@echo
+	@echo "Build finished."
+	@echo "To view the help file:"
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/flower"
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/flower"
+	@echo "# devhelp"
+
+epub:
+	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+	@echo
+	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo
+	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+	@echo "Run \`make' in that directory to run these through (pdf)latex" \
+	      "(use \`make latexpdf' here to do that automatically)."
+
+latexpdf:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through pdflatex..."
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+latexpdfja:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through platex and dvipdfmx..."
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+	@echo
+	@echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+	@echo
+	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+texinfo:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo
+	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
+	@echo "Run \`make' in that directory to run these through makeinfo" \
+	      "(use \`make info' here to do that automatically)."
+
+info:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo "Running Texinfo files through makeinfo..."
+	make -C $(BUILDDIR)/texinfo info
+	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
+
+gettext:
+	$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
+	@echo
+	@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
+
+changes:
+	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
+	@echo
+	@echo "The overview file is in $(BUILDDIR)/changes."
+
+linkcheck:
+	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
+	@echo
+	@echo "Link check complete; look for any errors in the above output " \
+	      "or in $(BUILDDIR)/linkcheck/output.txt."
+
+doctest:
+	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+	@echo "Testing of doctests in the sources finished, look at the " \
+	      "results in $(BUILDDIR)/doctest/output.txt."
+
+xml:
+	$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
+	@echo
+	@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
+
+pseudoxml:
+	$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
+	@echo
+	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."

flower_hierarchy-2.2.0.1/docs/_templates/localtoc.html

@@ -0,0 +1,4 @@
+{%- if display_toc %}
+  <h3><a href="{{ pathto(master_doc) }}">{{ _('Table Of Contents') }}</a></h3>
+  {{ toctree(collapse=False) }}
+{%- endif %}

flower_hierarchy-2.2.0.1/docs/_templates/page.html

@@ -0,0 +1,7 @@
+{% extends "layout.html" %}
+{% block body %}
+<div class="deck">
+
+</div>
+    {{ body }}
+{% endblock %}

flower_hierarchy-2.2.0.1/docs/_templates/sidebarintro.html

@@ -0,0 +1,8 @@
+<p>
+  <iframe src="http://ghbtns.com/github-btn.html?user=mher&repo=flower&type=watch&count=true&size=large"
+    allowtransparency="true" frameborder="0" scrolling="0" width="200px" height="35px"></iframe>
+</p>
+{%- if display_toc %}
+  <h3><a href="{{ pathto(master_doc) }}">{{ _('Table Of Contents') }}</a></h3>
+  {{ toctree(collapse=False) }}
+{%- endif %}

flower_hierarchy-2.2.0.1/docs/_templates/sidebarlogo.html

@@ -0,0 +1,4 @@
+<p>
+  <iframe src="http://ghbtns.com/github-btn.html?user=mher&repo=flower&type=watch&count=true&size=large"
+    allowtransparency="true" frameborder="0" scrolling="0" width="200px" height="35px"></iframe>
+</p>