ITR-tool
WWF version of the SBTi-Finance-tool, based on the CDP-WWF Temperature rating methodology
Visit https://wwf-sweden.github.io/ITR-tool/ for the full documentation
If you have any additional questions or comments send a mail to: ekonomi-finans@wwf.se
About the tool
This package helps companies and financial institutions to assess the temperature alignment of current targets, commitments, and investment and lending portfolios, and to use this information to develop targets for official validation by the SBTi.
The WWF Finance toolkit can be used in different ways:
- Users can integrate the Python package in their codebase
- Using Notebooks, either locally or on Google Colab
Structure
The folder structure for this project is as follows:
.
├── .github # Github specific files (Github Actions workflows)
├── docs # Documentation files (Sphinx)
├── config # Config files for the Docker container
├── ITR # The main Python package for the temperature alignment tool
└── test # Automated unit tests for the SBTi package (Nose2 tests)
Installation
The ITR package may be installed using PIP. If you'd like to install it locally use the following command. For testing or production please see the deployment section for further instructions
pip install -e .
For installing the latest stable release in PyPi run:
pip install wwf-itr
Development
To set up the local dev environment with all dependencies, install poetry and run
poetry install
This will create a virtual environment inside the project folder under .venv.
Testing
Each class should be unit tested. The unit tests are written using the Nose2 framework. The setup.py script should have already installed Nose2, so now you may run the tests as follows:
nose2 -v
Publish to PyPi
The package should be published to PyPi when any changes to main are merged.
Update package
- bump version in
pyproject.tomlbased on semantic versioning principles - run
poetry build - run
poetry publish - check whether package has been successfully uploaded
Initial Setup
- Create account on PyPi
Metadata
Release files for WWF-ITR 1.7.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 |
|---|---|---|---|---|
| wwf_itr-1.7.3.tar.gz | 1.8 MB | Without provenance | Details for wwf_itr-1.7.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wwf_itr-1.7.3-py3-none-any.whl | Python 3 | none | any | Details for wwf_itr-1.7.3-py3-none-any.whl |
Total release size: 3.5 MB
Release files / wwf_itr-1.7.3.tar.gz
| Download URL | wwf_itr-1.7.3.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d761ff5fc6b96b9b34bcfa223fe9568a5eba4ade2a2b64dc4634ad848a4ee681
|
|
BLAKE2b-256 checksum How to use checksums |
a6c9ff1cf1e2297c1ca83ac6ac598487bafd28cdd0d4896dbded075ba9eb35f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.12.1 Darwin/24.6.0
|
Release files / wwf_itr-1.7.3-py3-none-any.whl
| Download URL | wwf_itr-1.7.3-py3-none-any.whl |
|---|---|
| Size | 1.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cab7322ec0af01140806266b93aa9707fea15da431d591a273cfb5038e8d40f5
|
|
BLAKE2b-256 checksum How to use checksums |
3cb2d972734af6af622ef7f02387fae1114c377fcaf884bc66c14a0c0f8e258e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.12.1 Darwin/24.6.0
|
Security for WWF-ITR 1.7.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.