Re: Python module naming convention

[Leonardo Taccari <leot%NetBSD.org@localhost>]

Hello Frédéric, 

Frédéric Fauberteau writes:
> [...]
> I just added the python-digitalocean module as net/py-digitalocean 
> because I found that py-python- was redundant. I wanted to look at other 
> packages to see which master sites were used and I found that the guys 
> of FreeBSD ports chose www/py-python-digitalocean as name of package. 
> After inspecting our pkgsrc tree, I found some packages for which the 
> prefix python- was left in the name:
> * databases/py-python-sql
> * devel/py-python-dotenv
> * devel/py-python-slugify
> * lang/py-python-lua
> * lang/py-pythonz
> * www/py-python-digest
> * www/py-python-mimeparse
> * www/py-python3-digest
>
> Now, I think I should rename net/py-digitalocean in 
> net/py-python-digitalocean to respect the name of the module. Before 
> doing that, I would like to know if a convention is commonly used in 
> pkgsrc.
> [...]

I think that's a bit more cacophonic and redundant and usually you will
find a lot of Python packages were the extra `python-' is removed.

According a quick grep via:

 % ag -l -G Makefile -F 'MASTER_SITE_PYPI:=p/python-'

there are 34 packages in total with a `python-' prefix but in the
pkgsrc tree only 5 preserved the PKGPATH with `python-'.

At least in the previous list I think that:

 * lang/py-python-lua
 * lang/py-pythonz
 * www/py-python-digest
 * www/py-python3-digest

are in some ways special as all of them - when used through Python -
needs an `import python*' or similar (and also the `EGG_NAME' starts
with a `python').