On Thursday, October 9, 2025 2:15:52 AM Mountain Standard Time Jonathan Dowland wrote: > On Fri Oct 3, 2025 at 7:32 PM BST, Soren Stoutner wrote: > > On Friday, October 3, 2025 12:14:00 AM Mountain Standard Time Seyed Mohamad > > > > Amin Modaresi wrote: > >> I think it is not needed, because vkbasalt-cli python lib is not a > >> common library, the lib just can be used by vkbasalt-cli not the > >> others > > > > One of the important things in packaging for Debian is that packages need to > > work together in a larger ecosystem and follow established conventions for > > naming and contents. The established convention for Python packages is that > > all pure Python modules should be shipped in a separate package that begins > > with the python3- (or someday python4-). > > I don't think this is correct. Programs that have private modules are > not required to split them out into a separate library package. Indeed > doing so introduces unnecessary costs and overheads for the whole > project. Private modules are mentioned in § 5.3 > > https://www.debian.org/doc/packaging-manuals/python-policy/#programs-shipping-> private-modules I stand corrected. Thank you Jonathan. Seyed, after the package clears NEW you are welcome to combine it back into one binary package if you like. If you do so, according to the documentation linked above, you need to move the pure python modules from their current location in /usr/lib/python3/dist-packages/vkbasalt to /usr/share/vkbasalt or /usr/lib/vkbasalt. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.