Sample public project setup.
Usage
Add the package to your dependencies. If you’re working on a project managed by poetry, use the following:
$ poetry add public-test
If you’re working on a project managed by pipenv, use the following:
$ pipenv install public-test
After that, you should be able to import the library in your Python code:
from public_test import answer print(answer)
Development
This library itself is managed by poetry. Read the docs for basic usage. You can run tests like this:
$ poetry run pytest
To release a new version of the library, follow these steps:
Be sure to be on the master Git branch.
Decide whether your changes are breaking, improvement, or a bug fix. Use the poetry’s version command to raise the version number.
Read the new number from the poetry’s output and commit the change with git commit -am "release vX.Y.Z".
Tag the commit with git tag vX.Y.Z
Release a new version by pushing it all to GitHub: git push origin master --tags
The CI automatically builds the package and publishes it to the PyPI. New releases get listed at tags. If you like your colleagues, for each release click on Edit tag and write a title and description (changelog).
Automatic Releases
For the CI to be able to publish new releases to PyPI, a PYPI_TOKEN environment variable first needs to be set in the CircleCI project settings:
Read the docs about PyPI tokens and CircleCI project environment variables.
Generate a token at your PyPI account settings. Copy the token and treat it as a secret.
Go to CircleCI project settings, section Environment Variables, and add a new one called PYPI_TOKEN. Paste the token as a value.
Metadata
Release files for public-test 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 |
|---|---|---|---|---|
| public-test-0.1.1.tar.gz | 2.9 kB | Without provenance | Details for public-test-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| public_test-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for public_test-0.1.1-py3-none-any.whl |
Total release size: 6.6 kB
Release files / public-test-0.1.1.tar.gz
| Download URL | public-test-0.1.1.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55c7789ae65eaad74d4c02345c58d0715ccff917ebdbabdecba39aa9876a58b0
|
|
BLAKE2b-256 checksum How to use checksums |
026c52f464d2b5bb6446210e44fe1857dfb1ef719896badf759972b51dc8e69c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.6 Linux/4.15.0-1077-aws
|
Release files / public_test-0.1.1-py3-none-any.whl
| Download URL | public_test-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d09b0c52bc83ab43c821e2dd6217bb3201cdb2277d71e327a535c09e31cfc7a
|
|
BLAKE2b-256 checksum How to use checksums |
0d2396601a586b756e26b4e3559f364024427b2667071439bc99928e41b36176
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.6 Linux/4.15.0-1077-aws
|
Security for public-test 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.