asfexample
This package does not have official Apache Software Foundation (ASF) releases.
This is an example test package issued by Tooling at the ASF. It contains no stable user facing functionality. We do not make guarantees about any of the interfaces contained herein, nor the continued existence of this package.
The purpose of this package is to test:
- Proposed package naming conventions and version schemes within ASF Infra and ASF Tooling
- GHA workflows for trickle down use in other ASF Tooling projects
- Interaction with the ATR platform presently under development by ASF Tooling
Proposed conventions
The proposed packaging conventions are:
- Use
asf${NAME}or${NAME}for PyPI package names, depending on whether the package is for ASF use only or not - Ensure that package code is in
${NAME}/only - Use
0.0.Nfor versions, starting with0.0.1 - Increment
Nfor each released version - Use
0.0.(N+1).dev0+devfor non-releasemaincommits, starting with0.0.1.dev0+dev
The +dev makes it a local version, which PyPI will not accept, so a build from source can never be published as a release. The .dev0 makes it a pre-release, so installers that can see both choose the release.
A package having three commits on main, then a release, then two more commits to main, then another release, will for example use the following versions:
0.0.1.dev0+dev
0.0.1.dev0+dev
0.0.1.dev0+dev
0.0.1
0.0.2.dev0+dev
0.0.2.dev0+dev
0.0.2
These packaging conventions are proposed only for ASF Infra and Tooling packages which will be published to PyPI. Other packages, for internal use, may use any packaging conventions. Aligning with these conventions, if adopted, would, however, make it easier to promote internal packages to PyPI.
Releasing
To release 0.0.N, run uv version 0.0.N, commit, tag that commit v0.0.N, and push both together with git push --atomic origin main v0.0.N. A tag pushed on its own after its commit is not checked by the hooks.
The upload waits until two members of ASF Tooling approve it at https://releases.apache.org/gates.
Afterwards, run uv version 0.0.(N+1).dev0+dev with the next number filled in, commit, and push. Always set the version explicitly: uv version --bump stable keeps the +dev.
Development
Run uv run prek install once after cloning. Its hooks run the linters and check the version scheme on every commit, and add the type checks and tests on every push.
Metadata
Release files for asfexample 0.0.5
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 |
|---|---|---|---|---|
| asfexample-0.0.5.tar.gz | 9.4 kB | With provenance | Details for asfexample-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| asfexample-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for asfexample-0.0.5-py3-none-any.whl |
Total release size: 19.8 kB
Release files / asfexample-0.0.5.tar.gz
| Download URL | asfexample-0.0.5.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2ec68dac3d9f4f3253013558271aa5eb599b4413ec0373c4aacbab694480efe
|
|
BLAKE2b-256 checksum How to use checksums |
d4f1b14f4763d184deb72f28bc9e4f64db7288ef2197ba65fb2f4355abc09d2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logRelease files / asfexample-0.0.5-py3-none-any.whl
| Download URL | asfexample-0.0.5-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac8d4ed5f889427b7cee5003efeeb1d5d36028fc4ab594a2f49235ec1892901d
|
|
BLAKE2b-256 checksum How to use checksums |
aa7e5ce56dad14a4c19cee3a2837bd49e8d7e563d25dec7cfda261ccdeb20ef5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logSecurity for asfexample 0.0.5
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
Both files in this release have been uploaded with provenance metadata.
Attestation for asfexample-0.0.5.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 Nov 17, 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.