scalable-pypeline 1.1.0__tar.gz

scalable-pypeline-1.1.0/LICENSE

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

scalable-pypeline-1.1.0/MANIFEST.in

@@ -0,0 +1,6 @@
+include README.md
+include LICENSE
+include requirements.txt
+prune demo
+
+global-exclude *.c

scalable-pypeline-1.1.0/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.1
+Name: scalable-pypeline
+Version: 1.1.0
+Summary: PypeLine - Python pipelines for the Real World
+Home-page: https://gitlab.com/bravos2/pype-line
+Author: Bravos Power Corporation
+License: Apache License 2.0
+Description-Content-Type: text/markdown
+Provides-Extra: build
+Provides-Extra: cli
+Provides-Extra: flask
+Provides-Extra: flask_auth
+Provides-Extra: web
+Provides-Extra: workers
+Provides-Extra: dev
+Provides-Extra: test
+License-File: LICENSE
+
+# PypeLine
+
+## Quickstart
+
+1. Add `pypeline` as a dependency to your Python application
+1. Install extras depending on what you are building:
+
+1. `flask` - Convenient interface for Flask applications
+1. `web` - Some standard web server dependencies we like
+1. `workers` - Installs [Celery](https://docs.celeryproject.org/en/stable/getting-started/introduction.html) and [networkx](https://networkx.org/documentation/stable/index.html), which are required if using pipelines.
+
+## Overview
+
+PypeLines is a fork of [Sermos] (https://gitlab.com/sermos/sermos). PypeLines diverges from Sermos as a SAAS platform and is intented as a suite for job management in conjuction with or indepent from a Flask Web App. Common job management workflow's include running pipelines, scheduled tasks, and other various types of jobs. Pypelines is designed to make these systems faster and more intuitive to create for Python developers.
+
+Under the hood we are simply extending various Celery capabilities like their existing complex workflows and make them suitable for large scale pipelines that can be run in production. To do this PypeLines uses a custom Celery configuration and a library known as [Celery-Dyrygent](https://github.com/ovh/celery-dyrygent) to help orchestrate thousands of tasks at once.
+
+### Pypeline
+
+-   Celery Configuration
+-   Pipelines
+-   CronJobs
+-   APIs
+-   Utilities
+
+### Your Application
+
+This is where all of your code lives and only has a few _requirements_:
+
+1. It is a base application written in Python.
+1. Scheduled tasks and Pipeline nodes must be Python Methods that accept
+   at least one positional argument: `event`
+1. A `sermos.yaml` file, which is a configuration file for running scheduled tasks and pipelines.
+
+## Celery
+
+Pypelines provides sensical default configurations for the use of
+[Celery](http://www.celeryproject.org/). The default deployment uses RabbitMQ,
+and is recommended. This library can be implemented in any other workflow
+(e.g. Kafka) as desired.
+
+There are two core aspects of Celery that pypeline handles and differ from a
+standard Celery deployment.
+
+### ChainedTask
+
+In `celery.py` when imported it will configure Celery and also run
+`GenerateCeleryTasks().generate()`, which will use the `sermos.yaml` config
+to turn customer methods into decorated Celery tasks.
+
+Part of this process includes adding `ChainedTask` as the _base_ for all of
+these dynamically generated tasks.
+
+`ChainedTask` is a Celery `Task` that injects `tools` and `event` into the
+signature of all dynamically generated tasks.
+
+### SermosScheduler
+
+We allow users to set new scheduled / recurring tasks on-the-fly. Celery's
+default `beat_scheduler` does not support this behavior and would require the
+Beat process be killed/restarted upon every change. Instead, we set our
+custom `sermos.celery_beat:SermosScheduler` as the `beat_scheduler`,
+which takes care of watching the database for new/modified entries and reloads
+dynamically.
+
+## Workers / Tasks / Pipeline Nodes
+
+PypeLine handles decorating the tasks, generating the correct Celery
+chains, etc.
+
+Customer code has one requirement: write a python method that accepts one
+positional argument: `event`
+
+e.g.
+
+    def demo_pipeline_node_a(event):
+        logger.info(f"RUNNING demo_pipeline_node_a: {event}")
+        return
+
+### Generators
+
+_TODO_: This needs to be updated both in code and documentation. Leaving here
+because it's valuable to update in the future.
+
+A common task associated with processing batches of documents is generating
+the list of files to process. `pypeline.generators` contains two helpful
+classes to generate lists of files from S3 and from a local file system.
+
+`S3KeyGenerator` will produce a list of object keys in S3. Example:
+
+    gen = S3KeyGenerator('access-key', 'secret-key')
+    files = gen.list_files(
+        'bucket-name',
+        'folder/path/',
+        offset=0,
+        limit=4,
+        return_full_path=False
+    )
+
+`LocalKeyGenerator` will produce a list of file names on a local file system.
+Example:
+
+    gen = LocalKeyGenerator()
+    files = gen.list_files('/path/to/list/')
+
+## Testing
+
+If you are developing pypeline and want to test this package,
+install the test dependencies:
+
+    $ pip install -e .[test]
+
+Now, run the tests:
+
+    $ tox

scalable-pypeline-1.1.0/README.md

@@ -0,0 +1,115 @@
+# PypeLine
+
+## Quickstart
+
+1. Add `pypeline` as a dependency to your Python application
+1. Install extras depending on what you are building:
+
+1. `flask` - Convenient interface for Flask applications
+1. `web` - Some standard web server dependencies we like
+1. `workers` - Installs [Celery](https://docs.celeryproject.org/en/stable/getting-started/introduction.html) and [networkx](https://networkx.org/documentation/stable/index.html), which are required if using pipelines.
+
+## Overview
+
+PypeLines is a fork of [Sermos] (https://gitlab.com/sermos/sermos). PypeLines diverges from Sermos as a SAAS platform and is intented as a suite for job management in conjuction with or indepent from a Flask Web App. Common job management workflow's include running pipelines, scheduled tasks, and other various types of jobs. Pypelines is designed to make these systems faster and more intuitive to create for Python developers.
+
+Under the hood we are simply extending various Celery capabilities like their existing complex workflows and make them suitable for large scale pipelines that can be run in production. To do this PypeLines uses a custom Celery configuration and a library known as [Celery-Dyrygent](https://github.com/ovh/celery-dyrygent) to help orchestrate thousands of tasks at once.
+
+### Pypeline
+
+-   Celery Configuration
+-   Pipelines
+-   CronJobs
+-   APIs
+-   Utilities
+
+### Your Application
+
+This is where all of your code lives and only has a few _requirements_:
+
+1. It is a base application written in Python.
+1. Scheduled tasks and Pipeline nodes must be Python Methods that accept
+   at least one positional argument: `event`
+1. A `sermos.yaml` file, which is a configuration file for running scheduled tasks and pipelines.
+
+## Celery
+
+Pypelines provides sensical default configurations for the use of
+[Celery](http://www.celeryproject.org/). The default deployment uses RabbitMQ,
+and is recommended. This library can be implemented in any other workflow
+(e.g. Kafka) as desired.
+
+There are two core aspects of Celery that pypeline handles and differ from a
+standard Celery deployment.
+
+### ChainedTask
+
+In `celery.py` when imported it will configure Celery and also run
+`GenerateCeleryTasks().generate()`, which will use the `sermos.yaml` config
+to turn customer methods into decorated Celery tasks.
+
+Part of this process includes adding `ChainedTask` as the _base_ for all of
+these dynamically generated tasks.
+
+`ChainedTask` is a Celery `Task` that injects `tools` and `event` into the
+signature of all dynamically generated tasks.
+
+### SermosScheduler
+
+We allow users to set new scheduled / recurring tasks on-the-fly. Celery's
+default `beat_scheduler` does not support this behavior and would require the
+Beat process be killed/restarted upon every change. Instead, we set our
+custom `sermos.celery_beat:SermosScheduler` as the `beat_scheduler`,
+which takes care of watching the database for new/modified entries and reloads
+dynamically.
+
+## Workers / Tasks / Pipeline Nodes
+
+PypeLine handles decorating the tasks, generating the correct Celery
+chains, etc.
+
+Customer code has one requirement: write a python method that accepts one
+positional argument: `event`
+
+e.g.
+
+    def demo_pipeline_node_a(event):
+        logger.info(f"RUNNING demo_pipeline_node_a: {event}")
+        return
+
+### Generators
+
+_TODO_: This needs to be updated both in code and documentation. Leaving here
+because it's valuable to update in the future.
+
+A common task associated with processing batches of documents is generating
+the list of files to process. `pypeline.generators` contains two helpful
+classes to generate lists of files from S3 and from a local file system.
+
+`S3KeyGenerator` will produce a list of object keys in S3. Example:
+
+    gen = S3KeyGenerator('access-key', 'secret-key')
+    files = gen.list_files(
+        'bucket-name',
+        'folder/path/',
+        offset=0,
+        limit=4,
+        return_full_path=False
+    )
+
+`LocalKeyGenerator` will produce a list of file names on a local file system.
+Example:
+
+    gen = LocalKeyGenerator()
+    files = gen.list_files('/path/to/list/')
+
+## Testing
+
+If you are developing pypeline and want to test this package,
+install the test dependencies:
+
+    $ pip install -e .[test]
+
+Now, run the tests:
+
+    $ tox

scalable-pypeline-1.1.0/pypeline/__init__.py

@@ -0,0 +1 @@
+__version__ = '1.1.0'