This is an automated email from the ASF dual-hosted git repository.
sbp pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tooling-asf-example.git
The following commit(s) were added to refs/heads/main by this push:
new 017ef24 Update the proposed packaging conventions
017ef24 is described below
commit 017ef24b2229b6903d898bf0a999a8347c38018f
Author: Sean B. Palmer <[email protected]>
AuthorDate: Wed Dec 31 14:25:35 2025 +0000
Update the proposed packaging conventions
---
README.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index 19ac9ed..5a67605 100644
--- a/README.md
+++ b/README.md
@@ -14,10 +14,8 @@ The purpose of this package is to test:
The proposed packaging conventions are:
-- Use the `asf-*` prefix scheme for PyPI package names to align with PEP 752
-- Use `asf.*` for package interfaces, utilising PEP 420 namespacing
-- Ensure that package code is in `src/asf/*/` only
-- Ensure that `src/asf/*/` contains an `__init__.py`
+- 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.N` for versions, starting with `0.0.1`
- Increment `N` for each released version
- Optionally use `0.0.(N+1)-devM` for non-release `main` commits
@@ -35,4 +33,6 @@ A package having three commits on `main`, then a release,
then two more commits
0.0.2
```
+But there is a question of what to do about rebasing.
+
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
