[csw-maintainers] Change python modules catalog names to have a py_ prefix (instead of just py)?

Trygve Laugstol trygvis at opencsw.org
Mon Aug 24 12:38:40 CEST 2009

Maciej (Matchek) Blizinski wrote:
> On Mon, Aug 24, 2009 at 12:06 AM, Sebastian Kayser<skayser at opencsw.org> wrote:
>> Hi,
>> just wrote my first python module build description and noticed that
>> most of the few python modules in our catalog follow a catalog name
>> naming scheme of
>>  py<modulename>
>> With regards to user experience and consistency could we change the
>> default/standard to be more like the perl modules which have
>> pm_<modulename>? So for python modules this would be:
>>  py_<modulename>
> A question: Suppose the project's name is "pyfoo". (Like:
> http://pyyaml.org/) If we had py_projectname, it would end up being
> py_pyyaml. It looks a bit stupid. On the other hand, creating py_yaml
> makes the catalog name not containing the project name. If I tried
> doing pkg-get -a <projectname>, I wouldn't find the package. Which do
> you think is better?

If it is a product called "pyyaml" I would expect it to be called 
"pyyaml", but it was a library I would expect "py_pyyaml" (given that 
libraries should be called "py_*").


More information about the maintainers mailing list