expyriments
Organize, run, track and share experiments & data.
Getting Started • Features • Documentation • Support • Contribution • Changelog
TODO
Highlights
TODO
Getting Started
Installation
Requirements: Python 3.6+.
pip install expyriments
Usage
TODO
Support & Feedback
This project is maintained by Benjamin Räthlein, Lukas Masuch, and Jan Kalkan. Please understand that we won't be able to provide individual support via email. We also believe that help is much more valuable if it's shared publicly so that more people can benefit from it.
| Type | Channel |
|---|---|
| 🚨 Bug Reports | |
| 🎁 Feature Requests | |
| 👩💻 Usage Questions | |
| 🗯 General Discussion | |
| ❓ Other Requests |
Features
TODO
Documentation
CLI Interface
TODO
Python Client
TODO
Contribution
- Pull requests are encouraged and always welcome. Read our contribution guidelines and check out help-wanted issues.
- Submit Github issues for any feature request and enhancement, bugs, or documentation problems.
- By participating in this project, you agree to abide by its Code of Conduct.
- The development section below contains information on how to build and test the project after you have implemented some changes.
Development
Requirements: Docker and Act are required to be installed on your machine to execute the build process.
To simplify the process of building this project from scratch, we provide build-scripts - based on universal-build - that run all necessary steps (build, check, test, and release) within a containerized environment. To build and test your changes, execute the following command in the project root folder:
act -b -j build
Refer to our contribution guides for more detailed information on our build scripts and development process.
Licensed MIT. Created and maintained with ❤️ by developers from Berlin.
Metadata
Release files for expyriments 0.1.2
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 |
|---|---|---|---|---|
| expyriments-0.1.2.tar.gz | 2.2 MB | Without provenance | Details for expyriments-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| expyriments-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for expyriments-0.1.2-py3-none-any.whl |
Total release size: 4.4 MB
Release files / expyriments-0.1.2.tar.gz
| Download URL | expyriments-0.1.2.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
345be9f2b7d3d2909fe298a7e06d80601a9bdeb588fa42306d5e48b68d5cde66
|
|
BLAKE2b-256 checksum How to use checksums |
86700cb9c8892391d6aaf3f86de3c51f8c8769ed435d8488de56609138d13c62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.5
|
Release files / expyriments-0.1.2-py3-none-any.whl
| Download URL | expyriments-0.1.2-py3-none-any.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ac8fa310286caebe023d4514875e4e9278d6c1936ba15d4bb3e01d511ec94d3
|
|
BLAKE2b-256 checksum How to use checksums |
9884a24afddddbd93300101a685550d0458beb573c018fb79a1a53ed7988433f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.5
|
Security for expyriments 0.1.2
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.