Re: python package naming when upstream is inconsistent

[Joerg Sonnenberger <joerg%bec.de@localhost>]

Am Thu, Jun 16, 2022 at 12:16:57AM +0200 schrieb Thomas Klausner:
> On Wed, Jun 15, 2022 at 06:14:25PM -0400, Greg Troxel wrote:
> > 
> > I just packaged
> > 
> >   https://pypi.org/project/collections-extended/
> > 
> > which provides a python module
> > 
> >   collections_extended
> > 
> > and I named the package
> > 
> >   py-collections_extended
> > 
> > assuming that the PKGNAME should match the module name.  However, the
> > DISTNAME and PKGNAME are py-collections-extended, not matching PKGPATH.
> > 
> > 
> > This seems like an upstream misfeature, but maybe this is normal in
> > Python.
> > 
> > 
> > I am guessing I should change PKGPATH to devel/py-collections (by "cvs
> > mv" :-).  But I thought I should ask the python experts first.
> 
> Yes.
> 
> Please match the PKGNAME on what pypi recommends for "pip install", in
> this case
> 
> pip install collections-extended
> 
> i.e. py-collections-extended.

Agreed, generally that's the best idea, modulo dropping most initial
"python-" etc.

Joerg