Skip to main content

laforge is a low-key build system for working with data.

License: AGPL 3.0 Python: 3.6+ GitHub last commit Cat: Onigiri


💻 Introduction

You know, I've always thought technology could solve almost any problem.

$ python -m pip install laforge -q
...

$ laforge create
Creating /home/matvan/science/build.ini
? Creating a new laforge INI at:  /home/matvan/science/build.ini

Creating /home/matvan/science/build.ini

? Default read directory, relative to /home/matvan/science/:  ./data
? Default write directory, relative to /home/matvan/science/:  ./output
? Default execute directory, relative to /home/matvan/science/:  ./
? SQL Distribution:  SQLite
?     Database:  :memory:
New laforge INI written at: /home/matvan/science/build.ini
Enjoy!

There's theory and then there's application. They don't always jibe.

$ vim ./build.ini
...

$ cat ./build.ini
[DEFAULT]
read_dir: ./data
write_dir: ./output
execute_dir: ./
distro: sqlite
database: :memory:

# Write the contents of an Excel sheet as a SQL table
[load_individual]
read: 2019_indiv_data.xlsx
write: raw_grp

# Write the contents of a CSV as a SQL table
[load_group]
read: 2019_grp_data.csv
write: raw_indiv

# Execute a standalone SQL script; read a SQL table and save as CSV
[do_some_things]
execute: do_stuff.sql
read: laforge.demo.aggregate
write: aggregate.csv

# Read the result of an ad-hoc SQL query; write to an HTML table
[peek]
read:
    "select top 50 *
    from demo.aggregate agg
    left join demo.raw_indiv ri
        on agg.v1 = r1.v2
    order by newid();"
write: results_peek.html

Yeah, but that's imposs—yes, sir.

$ laforge build

‖-)

📓 Documentation

https://laforge.readthedocs.io/en/latest/

⚗️ Development

Captain, we can do it... It'll take fifteen years and a research team of a hundred.

Canonical repository at git.sr.ht.

Issue tracker at todo.sr.ht.

Core build service at builds.sr.ht.

Designed with Diet Coke.

🤖 Automation

LGTM Alerts

PyPI dependencies analysis at libraries.io

Documentation hosted on Read the Docs

Travis testing with coverage)

Coveralls coverage reporting

🚀 Downstream

GitHub tag (latest by date)

PyPI

🧙‍ Author

Matt VanEseltine

matvan@umich.edu

https://git.sr.ht/~matvan

https://github.com/vaneseltine

https://twitter.com/vaneseltine

Metadata

Release files for laforge 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for laforge 0.1.6
File Size Uploaded Provenance Actions
laforge-0.1.6.tar.gz 50.7 kB Without provenance Details for laforge-0.1.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for laforge 0.1.6
File Interpreter ABI Platform Actions
laforge-0.1.6-py3-none-any.whl Python 3 none any Details for laforge-0.1.6-py3-none-any.whl

Total release size: 119.0 kB

Release files / laforge-0.1.6.tar.gz

Download URL laforge-0.1.6.tar.gz
Size 50.7 kB
Tags Source
SHA-256 checksum
How to use checksums
a440098d54d4523e8dec329f7152dae98939e0b58583062f65a5cf280b481a84
BLAKE2b-256 checksum
How to use checksums
110eb6f2891d06ebddf11e61d52fff6531d7dd0d865227c09c667a059877fe13
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3

Release files / laforge-0.1.6-py3-none-any.whl

Download URL laforge-0.1.6-py3-none-any.whl
Size 68.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bdf599277c86123534cbd0bfa3cef46896dd7aad294b73a5f501fee3e8b6bee0
BLAKE2b-256 checksum
How to use checksums
feef14c5ec4db91a2c30e34ed5abf581d8a42c30fe9224732d66e915dc25916c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3

Security for laforge 0.1.6

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page