+1
Seems like Alexander did exactly that.
In the meantime we spent some time with Alex to understand why poetry and
also uv actually create files with underscores, not hyphens, for the name
part of the filename:
apache_otava-0.6.0-rc5.tar.gz
Looking at random pypi.org packages, this really seems to be common: The
package name might be "soil-fertilizer", and you'd use it both in "npm
install soil-fertilizer" and https://pypi.org/project/soil-fertilizer
However, the actual tar.gz and *.whl filenames change that to snake case:
soil_fertilizer-0.6.0.tar.gz
We will of course use that format too.
I've thought about it and I think the project name guidelines I read were
referring to some kind of official name of a package, and my conjecture
that also the tar archive name should follow the same rules was naive. To
summarize what we see happening:
- You are free to use - _ and capital letters in your project name, as you
prefer
- npm and other tools, will force that to "soil-fertilized"
- build tools like poetry will produce files where hyphens have been
forced to become underscores: soil_fertilizer-0.1.0...
- It's worth noting that "import soil-fertilizer" isn't valid python
syntax. So in the code, snake case is more useful.
henrik
On Thu, Jun 5, 2025 at 9:34 AM Mick Semb Wever <m...@apache.org> wrote:
> > But I would consider using the word "incubating" either in the
> > authors or description fields, or both:
> >
> > description = "Apache Otava Incubator project: Change Detection for
> > Continuous Performance Engineering"
> > authors = ["Apache Otava Incubator <dev@otava.apache.org>"]
> >
>
>
> Yes please do.
> It shows you're following the intent of clearly labelling the project and
> these versions as currently part of the Apache Incubator.
>
> Given that the pypi/ files are only convenience artefacts, and won't be
> part of the post-vote /dist asf download, do you have a script ready for
> post-vote to upload those pypi/ files from their dev svn location to pypi ?
>
