Lagranto - A Library to work with trajectories.
A recent build of the documentation is available at https://lagranto.readthedocs.io/en/latest/
Changelog
The changelog of can be found under CHANGELOG.md.
Install the development environment
Copy locally the latest version from lagranto:
git clone git@git.iac.ethz.ch:atmosdyn/Lagranto.git /path/to/local/lagranto
cd path/to/local/lagranto
Prepare the conda environment:
module load miniconda3
conda create -y -q -n lagranto_dev python=3.5.4 pytest
conda env update -q -f lagranto.yml -n lagranto_dev
Install lagranto in development mode in lagranto_dev:
source activate lagranto_dev
pip install -e .
Run the tests:
python -m pytest
Make the modifications available
git clone URL # Copy the server version locally
git status # Give the status of the file as seen from git
git pull # Get the latest version from the server
git add FILES... # Add modified files
git commit # Add the changes to the git system, only locally
git push # Push the local changes to the server
Documentation
To compile the documentation the sphinx package have to be installed:
conda install sphinx
To compile the html documentation:
cd docs
make html
Update package on conda and PyPi
Prerequisites
Conda
A github account
Fork the repository https://github.com/conda-forge/lagranto-feedstock.
Clone the fork locally.
PyPi
A PyPi account
A gpg key
General Steps
Change the version number in setup.py
Add a tag for this new version:
git tag -s TAGNAME -u KEY
Push the tag:
git push --tags
PyPi
Simply run:
./pypi_upload.sh
Conda
Edit the version name and the sha256 sum of Lagranto in recipe/meta.yaml. The sha256 can be determined as follow:
wget "https://git.iac.ethz.ch/atmosdyn/Lagranto/repository/VERSION/archive.tar.gz"
sha245sum archive.tar.gz
Commit and push the changes, and on github create a pull-request on conda-forge/lagranto-feedstock
Metadata
Release files for Lagranto 0.3.1
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 |
|---|---|---|---|---|
| Lagranto-0.3.1.tar.gz | 1.2 MB | Without provenance | Details for Lagranto-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Lagranto-0.3.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for Lagranto-0.3.1-py2.py3-none-any.whl |
Total release size: 1.3 MB
Release files / Lagranto-0.3.1.tar.gz
| Download URL | Lagranto-0.3.1.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f0a7055879d55710e47f0bfcfd0a0a64635459a233371fcc3bc52281db81dd1
|
|
BLAKE2b-256 checksum How to use checksums |
c6539616fb0d1ea5fcf4075542e9c24db04ee27ce4940a85dcb428e8ebd3b527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/0.0.0 pkginfo/1.8.2 readme-renderer/27.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.4.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Release files / Lagranto-0.3.1-py2.py3-none-any.whl
| Download URL | Lagranto-0.3.1-py2.py3-none-any.whl |
|---|---|
| Size | 32.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e65caa2eebdebf60c0d7ca6da8e6a38a77682de195885f15e9323776b76468d3
|
|
BLAKE2b-256 checksum How to use checksums |
33d1496418b2acbfe9d166cd3d7b63253a087bb0509b00ebe0d7ef1965cc6ae9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/0.0.0 pkginfo/1.8.2 readme-renderer/27.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.4.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for Lagranto 0.3.1
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.