[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Need help with naming scheme in debian/control for python library



Hi Carsten, just went through the link you sent and noticed that a lot of the packages inside just have the name in the form “packagename” 

But my wnpp ITP has the package name as “python3-packagename”. Should I modify the ITP request to read it as “python-packagename” too?

a simple “packagename” might conflict with other existing non python package due to similar names

Get Outlook for iOS

From: Aryan Karamtoth <aryankmmiv@outlook.com>
Sent: Tuesday, July 1, 2025 2:32:24 PM
To: Carsten Schoenert <c.schoenert@t-online.de>; debian-python@lists.debian.org <debian-python@lists.debian.org>
Subject: Re: Need help with naming scheme in debian/control for python library
 
I read somewhere in some documentation given by Debian Python Team and they said that “python-packagename” stands for a library in Python 2 and “python3-packagename” must be the convention for python 3 librarie.

From: Carsten Schoenert <c.schoenert@t-online.de>
Sent: Tuesday, July 1, 2025 2:12:19 PM
To: Aryan Karamtoth <aryankmmiv@outlook.com>; debian-python@lists.debian.org <debian-python@lists.debian.org>
Subject: Re: Need help with naming scheme in debian/control for python library
 
Hello Aryan,

Am 01.07.25 um 09:59 schrieb Aryan Karamtoth:
...
> So my question is should I rename the source field to “python3-
> packagename” too or will it cause any conflicts?

the common sense is to prefix the source package with "python" without
any version numbers.

And the bin package for a library with "python3" to mark the Paython
main version the package is usable with.

Contrary bin packages which contain documentation only then get the
prefix "python" again, but also a suffix "doc".

e.g.

Source: python-upstream_name
...

Package: python3-upstream_name
Description: Shiny neat Python library to do $things
...

Package: python-upstream_name-doc
Description: Shiny neat Python library to do $things (Documentation)
...

https://qa.debian.org/developer.php?email=team%2Bpython%40tracker.debian.org

There you have a full overview of existing packages maintained by the DPT.
Have a look at existing packages.


--
Regards
Carsten


Reply to: