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
