repo2env
Determine the environment specification for a given (app) repository.
This tool parses an (app) repository and determines requirements similar to repo2docker. But instead of generating a docker image it returns a specification that can then be used to build the environment.
Installation
The easiest way to install this tool is either directly with pip:
~ $ pip install git+https://github.com/aiidalab/repo2env.git
Or clone the repository first and then install:
~ $ git clone https://github.com/aiidalab/repo2env.git
~ $ cd repo2env/
~/repo2env $ pip install .
Usage
Use the repo2env command to parse the environment of a local or remote (app) repository:
For a local repository, just provide the path:
~ $ repo2env /path/aiidalab-hello-world/
{"python_requirements": ["aiidalab>=20.02.0b2"]}
For a remote repository, provide a PEP 508 compliant URL, for example:
~ $ repo2env git+https://github.com/aiidalab/aiidalab-hello-world.git@v1.0.0
{"python_requirements": ["aiidalab>=20.02.0b2"]}
The output is JSON-formatted and can then be used for further processing.
Tip: Use jq to generate pretty-printed output for manual inspection:
$ repo2env ~/local/aiidalab/aiidalab-hello-world/ | jq .
{
"python_requirements": [
"aiidalab>=20.02.0b2"
]
}
What is parsed
setup.cfg: If present, theoptions.install_requireslist is parsed intopython_requirements.requirements.txtIs parsed intopython_requirementsif present andsetup.cfgis not present.
Acknowledgements
This work is supported by the MARVEL National Centre for Competency in Research funded by the Swiss National Science Foundation, as well as by the MARKETPLACE project funded by Horizon 2020 under the H2020-NMBP-25-2017 call (Grant No. 760173).
Metadata
Release files for repo2env 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 |
|---|---|---|---|---|
| repo2env-0.1.2.tar.gz | 6.7 kB | Without provenance | Details for repo2env-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repo2env-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for repo2env-0.1.2-py3-none-any.whl |
Total release size: 14.8 kB
Release files / repo2env-0.1.2.tar.gz
| Download URL | repo2env-0.1.2.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96e96d3c0307e1c8cbae04d2a22e160d7c27185db43be895254cff3b41fe54b9
|
|
BLAKE2b-256 checksum How to use checksums |
c55698b866fcabdcd55a16361d4dd372e24b16a817d1aff0ef8e0a7f25974508
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.1 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.7.10
|
Release files / repo2env-0.1.2-py3-none-any.whl
| Download URL | repo2env-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d8172562d948530069bf31d86a40a0f600b11038a6a352ada2d8dcf8eeee37e
|
|
BLAKE2b-256 checksum How to use checksums |
627a671f55207e13ba5e0d6c8ff7e720319f9e25b4412ddd304123841c6ff0f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.1 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.7.10
|
Security for repo2env 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.