Groups > linux.debian.maint.python > #17395

Is pip(x) used internally while Debian packaging?

Path	csiph.com!pasdenom.info!newsfeed.bofh.team!3.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	<c.buhtz@posteo.jp>
Newsgroups	linux.debian.maint.python
Subject	Is pip(x) used internally while Debian packaging?
Date	Sat, 14 Feb 2026 13:10:03 +0100
Message-ID	<MomDh-wyY-53@gated-at.bofh.it> (permalink)
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Sat Feb 14 12:00:12 2026
Old-Return-Path	<c.buhtz@posteo.jp>
X-Amavis-Spam-Status	No, score=-9.297 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .posteo. - helo: .mout02.posteo. - helo-domain: .posteo.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
Reply-To	debian-python@lists.debian.org
MIME-Version	1.0
Content-Type	text/plain; charset=US-ASCII
Content-Transfer-Encoding	7bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23654
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/4fCndy21GYz9rxK@submission02.posteo.de
Approved	robomod@news.nic.it
Lines	26
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sat, 14 Feb 2026 11:59:50 +0000
X-Original-Message-ID	<4fCndy21GYz9rxK@submission02.posteo.de>
Xref	csiph.com linux.debian.maint.python:17395

Show key headers only | View raw

Hello Folks,
from my perspective as upstream maintainer I try to learn some
internals.

Imagine a modern Python application following PEP 517 & 621
(pyproject.toml and src-layout). Translations are handled via GNU
gettext. Hatch(ling) is used as build system using "initialize" build
hook to compile po into mo files and add them into the wheel.
The application does access them via "importlib.resources".

How does this interfere with Debian packaging?
I don't want to create extra work for people like you.

In a Debian package the mo files do not belong into the wheel but into
/usr/share/locale.

Is the Python build system relevant while Debian packing? Is pip used
internally while you create the deb file? Or do you use your own way
and the build system used by upstream does not matter?

I know you have a lot of tools to add extra ways and exceptions to
overwrite upstream behavior. But I want to prevent that, spare your
time and make it right from the very first beginning.

Regards,
Christian Buhtz

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar

Thread

Is pip(x) used internally while Debian packaging? <c.buhtz@posteo.jp> - 2026-02-14 13:10 +0100
  Re: Is pip(x) used internally while Debian packaging? Mechtilde Stehmann <mechtilde@debian.org> - 2026-02-14 14:40 +0100
    Re: Is pip(x) used internally while Debian packaging? c.buhtz@posteo.jp - 2026-02-14 17:10 +0100
  Re: Is pip(x) used internally while Debian packaging? Stefano Rivera <stefanor@debian.org> - 2026-02-14 15:00 +0100

csiph-web