baf - example packaging layout
baf is an example python packaging layout by @kvbik
i’ve read multiple setup.py files, blogposts and articles, spoken to multiple people, deployed multiple packages
and i want to share a packaging layout that i come up with
it’ll get change in the future i think as my and python preference get changed and you can of course discuss features or even send pull requests..
https://github.com/kvbik/python-baf/issues
other most important web sources are:
1 maintainer
Metadata
1 maintainer
Release files for baf 1.0
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 | |
|---|---|---|---|---|
| baf-1.0.tar.gz | 1.9 kB | Without provenance | Details |
Release files / baf-1.0.tar.gz
| Download URL | baf-1.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84f752839389058b1516f9a468a7851b624a51c19b4bc1919dd501d495ea13e4
|
|
BLAKE2b-256 checksum How to use checksums |
8183a3cb346720c0a018d017bbb46b8c82e555169091612f893488e32d2fd531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for baf 1.0
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.
