lippertzpy
Python helpers for the Jifeline Partner API and local logging.
Installation
After publication on PyPI:
python -m pip install lippertzpy
Upgrade to the latest published version:
python -m pip install --upgrade lippertzpy
Installation directly from GitHub remains possible:
python -m pip install git+https://github.com/R0g3rT/lippertzPy.git
For local development:
python -m pip install -e .
Usage
from lippertzpy import get, post, write_log
write_log("API client gestartet")
result = get("endpoint")
result = post("endpoint", {"data": data})
The package exports the Jifeline API helpers get, post, put, delete and get_access_token, as well as the logging helpers setup_logging and write_log.
Configuration
Copy .env.example to your-script-folder\.env or create a file .env in your directory and enter your credentials.
Do not commit your real .env file or credentials to GitHub.
Documentation
1 maintainer
Metadata
1 maintainer
Release files for lippertzpy 0.1.4
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 |
|---|---|---|---|---|
| lippertzpy-0.1.4.tar.gz | 3.9 kB | With provenance | Details for lippertzpy-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lippertzpy-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for lippertzpy-0.1.4-py3-none-any.whl |
Total release size: 7.8 kB
Release files / lippertzpy-0.1.4.tar.gz
| Download URL | lippertzpy-0.1.4.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d3581a9aa0a4e404cb9c80297e9118c2f26c4c0ab045f2d5c3e907251bb5ccd
|
|
BLAKE2b-256 checksum How to use checksums |
86f29374c1cce4dbb5175b06d9531ee1ec8b9b0ed4cb79573132db95c42d4027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logRelease files / lippertzpy-0.1.4-py3-none-any.whl
| Download URL | lippertzpy-0.1.4-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd610762da2e2ef16a24111a16563613f5e4ef2e4843d8da2a8380f9ddb9a7af
|
|
BLAKE2b-256 checksum How to use checksums |
56d5a33aa47cb911554f54c3f445b01cda01e59d274d25a590f2d2d97070ff34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logSecurity for lippertzpy 0.1.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lippertzpy-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logA 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.
