enetpy
Python wrapper for the ene't Marktpartner API
Setup
Install the package:
pip install enetpy
Make sure to set the authentication token in your production environment.
export ENET_AUTH_TOKEN='****'
Testing
The API wrapper comes with a testing stub. To use it set your test environment to:
export ENET_TESTING_STUB=1
Usage
>>> from enet import api
>>> api.get_gas_grid_operator_for_address(
... zip_code='10115',
... city='Berlin',
... street='Brunnenstr.',
... house_number='153'
... )
GasGridOperator(vnbg_nr=107851, title='NBB Netzgesellschaft Berlin-Brandenburg mbH & Co. KG', email='netzzugang@nbb-netzgesellschaft.de', contact_name='Herr Cornelius Baumann', phone_number='030/81876-1382', fax_number='', gas_type='H-Gas')
Release files for enetpy 1.0.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 | |
|---|---|---|---|---|
| enetpy-1.0.1.tar.gz | 8.9 kB | Without provenance | Details |
Release files / enetpy-1.0.1.tar.gz
| Download URL | enetpy-1.0.1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5684600e4bf1c5e867bfad531c6b30625fd430d89b7c47ebde769f7843b6937
|
|
BLAKE2b-256 checksum How to use checksums |
de7222df7e8774f8c4f63907b5148f3e3a06c174876013f6ad6e29f057ef1664
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.0
|
Security for enetpy 1.0.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.
