View: |
Part 1: Document Description
|
Citation |
|
---|---|
Title: |
PyPlant: A Python Framework for Cached Function Pipelines |
Identification Number: |
doi:10.18419/darus-2249 |
Distributor: |
DaRUS |
Date of Distribution: |
2022-01-24 |
Version: |
1 |
Bibliographic Citation: |
Tkachev, Gleb, 2022, "PyPlant: A Python Framework for Cached Function Pipelines", https://doi.org/10.18419/darus-2249, DaRUS, V1 |
Citation |
|
Title: |
PyPlant: A Python Framework for Cached Function Pipelines |
Identification Number: |
doi:10.18419/darus-2249 |
Authoring Entity: |
Tkachev, Gleb (Universität Stuttgart) |
Grant Number: |
EXC 2075 - 390740016 |
Distributor: |
DaRUS |
Access Authority: |
Tkachev, Gleb |
Access Authority: |
Tkachev, Gleb |
Depositor: |
Tkachev, Gleb |
Date of Deposit: |
2021-11-26 |
Holdings Information: |
https://doi.org/10.18419/darus-2249 |
Study Scope |
|
Keywords: |
Computer and Information Science |
Topic Classification: |
Development frameworks and environments |
Abstract: |
PyPlant is a simple coroutine-based framework for writing data processing pipelines. PyPlant's goal is to simplify caching of intermediate results in the pipeline and avoid re-running expensive early stages of the pipeline, when only the later stages have changed. |
Notes: |
<p>PyPlant is a simple coroutine-based framework for writing data processing pipelines. <br/> Given a set of Python functions that consume and produce data, it automatically runs them in a correct order and caches intermediate results. When the pipeline is executed again, only the necessary parts are re-run.</p> <p>Importantly, PyPlant was designed with the following design consideration in mind: <ul> <li>Simple: Quick to learn, no custom language and workflow design programs. Start prototyping right away.</li> <li>DRY: Function code is metadata. No need to write execution graphs or external metadata. It just works (tm).</li> <li>Automatic: No need to manually re-run outdated parts.</li> <li>Large data: Handle data that doesn't fit into memory. Persist between runs.</li> </ul> <p>PyPlant can be installed from PyPI: `pip install pyplant`<br> For documentation, see <a href="https://darus.uni-stuttgart.de/file.xhtml?fileId=70090&version=DRAFT">README.md</a>.</p> |
Methodology and Processing |
|
Sources Statement |
|
Data Access |
|
Other Study Description Materials |
|
Label: |
.gitignore |
Notes: |
application/octet-stream |
Label: |
.travis.yml |
Notes: |
application/octet-stream |
Label: |
LICENSE.txt |
Notes: |
text/plain |
Label: |
README.md |
Notes: |
text/markdown |
Label: |
requirements.txt |
Notes: |
text/plain |
Label: |
roadmap.txt |
Notes: |
text/plain |
Label: |
setup.cfg |
Notes: |
application/octet-stream |
Label: |
setup.py |
Notes: |
text/x-python |
Label: |
pyplant.py |
Notes: |
text/x-python |
Label: |
specs.py |
Notes: |
text/x-python |
Label: |
utils.py |
Notes: |
text/x-python |
Label: |
__init__.py |
Notes: |
text/x-python |
Label: |
PipeworkMock.py |
Notes: |
text/x-python |
Label: |
test_utils.py |
Notes: |
text/x-python |
Label: |
__init__.py |
Notes: |
text/x-python |
Label: |
pyplant_test.py |
Notes: |
text/x-python |
Label: |
utils_test.py |
Notes: |
text/x-python |