Re: [gentoo-dev] dev-python/ package naming policy?

[Michał Górny]

On Sat, 2023-01-28 at 17:38 +0100, Michał Górny wrote:
> To improve consistency and make packages easier to find, I'd like to
> propose going forward that when packages are published on PyPI, we use
> their official PyPI names.  This also means preserving the case for
> the few packages that use CamelCase names and similar.
>
> Some modifications will be necessary.  For example, it is legal for PyPI
> package names to include dot (".") — we normally translate that to a
> hyphen ("-").  We may also have use cases for creating multiple Gentoo
> packages from the same PyPI package (see e.g. dev-python/ensurepip-*).
> Then, there are of course Python packages that aren't published on PyPI.
>
> Still, I think as a general rule of thumb this would make sense.  WDYT?
>

To add a data point, the "Flask-Babel" package has been renamed to
"flask-babel" upstream today.  Unfortunately, minor changes to names are
not that uncommon (pkgcheck regularly catches them via "mismatched"
remote-ids).  This also means that now this one package is inconsistent
with the rest of capitalized "Flask" packages.

In the end, I'm still not sure whether this policy really makes sense. 
Perhaps it should be relaxed to allow case mismatches, if only to allow
us to retain in-tree consistency when upstreams fail to be consistent.

However, there's a can of worms around the corner -- should we also
allow normalizing "-" and "_" across different packages (see dev-
python/sphinx*)?

Now you see why we didn't have a policy for this before.

-- 
Best regards,
Michał Górny