Publishing LoggingLib with Poetry
This guide will walk you through the steps to publish your Python package using Poetry. Poetry is a dependency management and packaging tool for Python projects.
Prerequisites
-
Poetry Installed: Make sure Poetry is installed on your system. You can install it by following the instructions on the Poetry official website.
-
PyPI Account: Ensure you have an account on PyPI. You'll need your username and password for publishing.
Steps to Publish a Python Package
1. Build Your Package
Navigate to your project directory and run the following command to build your package:
poetry build
This command will generate distribution archives (e.g., .whl and .tar.gz files) in the dist directory.
2. Publish Your Package
To publish your package to PyPI, use the following command:
poetry publish --username <your-username> --password <your-password>
Alternatively, you can use the --build option to build and publish your package in one step:
poetry publish --build --username <your-username> --password <your-password>
3. Using PyPI Token
For better security, you can use an API token instead of your username and password. First, generate an API token from your PyPI account settings.
Then, you can publish your package using the token:
poetry publish --build --username __token__ --password <your-token>
4. Publishing to TestPyPI (Optional)
Before publishing to the official PyPI repository, you might want to publish to TestPyPI to test your package.
To publish to TestPyPI, use the following command:
poetry publish --build --repository testpypi --username <your-username> --password <your-password>
To use an API token with TestPyPI:
poetry publish --build --repository testpypi --username __token__ --password <your-token>
Metadata
Release files for logginglib 0.1.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 |
|---|---|---|---|---|
| logginglib-0.1.1.tar.gz | 3.3 kB | Without provenance | Details for logginglib-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logginglib-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for logginglib-0.1.1-py3-none-any.whl |
Total release size: 7.1 kB
Release files / logginglib-0.1.1.tar.gz
| Download URL | logginglib-0.1.1.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
872cfddefc8132feebb1633ccfae08ea69a6fb32d3cd4d37c40048946e9319bc
|
|
BLAKE2b-256 checksum How to use checksums |
665b6a147fcd5a01621c11be47ad7bcff77dfedf80c24fe4417c06a642a74778
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.10.12 Linux/6.5.0-41-generic
|
Release files / logginglib-0.1.1-py3-none-any.whl
| Download URL | logginglib-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
086bd1f6a74b5c01342f2feb3f1510f8e593bdb7d32a3d396b5ecc573ff9c585
|
|
BLAKE2b-256 checksum How to use checksums |
3df86187df44673d9fac339d09888fedce3d5e3f490360a4eb596f746f873719
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.10.12 Linux/6.5.0-41-generic
|
Security for logginglib 0.1.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.