* Package name    : environs
  Version         : 15.0.1
  Upstream Contact: Steven Loria <git@stevenloria.com>
* URL             : https://github.com/sloria/environs
* License         : MIT
  Programming Lang: Python
  Description     : Python library for parsing environment variables

environs is a Python library for parsing environment variables. It
provides more functionality compared to os.environ like casting,
validation and defaults. It integrates well with Flask and Django.

I plan to maintain this package under the Python Team umbrella. I will
need a sponsor for this package.

Hi!

The name of this package is extremely generic. Given that this is a
python module, please namespace both source and binary packages
accordingly.

Thanks,
Guillem

Hi Guillem

(dropping debian-devel)

Thanks for pointing this problem out to me here and in #1134759 for
markdown-pdf.

I was a bit surprised to see many python source packages to not have a
python- prefix, whereas the binary packages are typically prefixed with
python3-. Is there a reason for this difference?

In these two particular cases, do I prefix the source packages with
python-, python3-, or py-? Since the repos on Salsa would be in the
Debian Python team namespace, should the repo names also have a prefix
or can I drop it there?

Thanks for your help.

Best,

Hi!

Unfortunately the python team has never enforced this, unlike pretty
much every other language team in Debian (perl, ruby, lua, java,
javascript, golang, rust, etc).

There's https://bugs.debian.org/791635 which I should follow up on,
but I don't think it was ever received with much enthusiasm, so it's
not been very motivating.

I think the current convention for namespaced python modules/libraries
is that source packages are prefixed with python- and binary packages are
currently prefixed with python3 (they were previously prefixed with
python2- for example).

As an aside, I've got a WIP change for dpkg [S], to automatically provide
default values for the Section field based on at least the Source and
Package fields, where for python, the only patterns recognized are
those two.

[S] https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/commit/?h=next/default-field-values&id=e38ac13671d4b7767da1f2063cab640dfac50bc4

Thanks,
Guillem

Hi Alex, Guillem,

With regards to the binary package names, the Debian Python Policy is
even explicit [1] on the prefix, here 'python3-'.

I couldn't find anything on the source package name but I agree with
Guillem that the convention is to prefix with 'python-', unless the name
is unique/specific/established enough for confusion to be unlikely (see
for example src:twisted and src:sqlalchemy).

Best,
Christian

[1]: https://www.debian.org/doc/packaging-manuals/python-policy/#module-package-names