Seesaw toolkit
An asynchronous toolkit for distributed web processing. Written in Python and named after its behavior, it supports concurrent downloads, uploads, etc.
This toolkit is well-known for Archive Team projects. It also powers the Archive Team warrior.
Installation
Requires Python 2 or 3.
Needs the Tornado library for event-driven I/O. The complete list of Python modules needed are listed in requirements.txt.
How to try it out
To run the example pipeline:
sudo pip install -r requirements.txt
./run-pipeline --help
./run-pipeline examples/example-pipeline.py someone
Point your browser to http://127.0.0.1:8001/.
You can also use run-pipeline2 or run-pipeline3 to be explicit for the Python version.
Overview
General idea: a set of Tasks that can be combined into a Pipeline that processes Items:
- An
Itemis a thing that needs to be downloaded (a user, for example). It has properties that are filled by theTasks. - A
Taskis a step in the download process: it takes an item, does something with it and passes it on. Example Tasks: getting an item name from the tracker, running a download script, rsyncing the result, notifying the tracker that it's done. - A
Pipelinerepresents a sequence ofTasks. To make a seesaw script for a new project you'd specify a newPipeline.
A Task can work on multiple Items at a time (e.g., multiple Wget downloads). The concurrency can be limited by wrapping the task in a LimitConcurrency Task: this will queue the items and run them one-by-one (e.g., a single Rsync upload).
The Pipeline needs to be fed empty Item objects; by controlling the number of active Items you can limit the number of items. (For example, add a new item each time an item leaves the pipeline.)
With the ItemValue, ItemInterpolation and ConfigValue classes it is possible to pass item-specific arguments to the Task objects. The value of these objects will be re-evaluated for each item. Examples: a path name that depends on the item name, a configurable bandwidth limit, the number of concurrent downloads.
Consult the wiki for more information.
Metadata
Release files for seesaw2 0.10.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| seesaw2-00.10.3.tar.gz | 152.7 kB | Without provenance | Details for seesaw2-00.10.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seesaw2-00.10.3-py3-none-any.whl | Python 3 | none | any | Details for seesaw2-00.10.3-py3-none-any.whl |
Total release size: 302.5 kB
Release files / seesaw2-00.10.3.tar.gz
| Download URL | seesaw2-00.10.3.tar.gz |
|---|---|
| Size | 152.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9827c5e02387c85a612221e84841c0e16d3ecbd452989cae7a6e6048acaa8429
|
|
BLAKE2b-256 checksum How to use checksums |
d6b1cf4af0a5f5c07ef6799c057825793f60217fed5694367f33193f27ab0ee8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.7
|
Release files / seesaw2-00.10.3-py3-none-any.whl
| Download URL | seesaw2-00.10.3-py3-none-any.whl |
|---|---|
| Size | 149.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f83949e4171f3b3202b226067f313ce41014829d6a9c8efb3d66973cac0dfb62
|
|
BLAKE2b-256 checksum How to use checksums |
b899115473a5c2b482728b4c335c8afa67a0b5fa8c7098920e5cca4ad760ea52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.7
|
Security for seesaw2 0.10.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.