On Fri, Aug 16, 2024 at 02:52:25AM +0200, Philippe Cerfon wrote:

Hey.

I'm already using dh_python for (Python) packages where I have a pyproject.toml with some [project.scripts] section and use
python3-setuptools for building, which works quite nicely.

Now I do have some standalone python scripts for which it makes not
much sense to make them (Python) packages (i.e. there's no
__init__.py, etc.), yet I'd still like to have stuff like
automatically getting the right Debian package dependencies in a
Debian package.

If there is no metadata there is no "automatically getting the right
Debian package dependencies".

b) the Debian packge has none of the python packages/modules that I
import auto-detected as dependencies

This is not done even for module packages.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAma+7BMtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh WbEP/1THH6P6+oTj5ZpPO/uHaB10vJcdva+WI0XO5wkGQ1qTfL6irZk6jo9POLSj 5OPRocX8NL7s4YTUnslwjjreT+Ko1HF2503xD/4SIGYZyFDc8JTvKncQ4wdQCLoh Vl0o+DG/rFT4rWFc18xm+6I7RrLBNXk6JGHriSFrQBu3eYoMAK0VRFbibaB48llS K1jC+f+f7h+NpJG7FDoEAkeavLTwur79crQD1rn55/mJDiNt1zdY/L00QAD8Bcsh RiWNY7YjKnXlOPkH0wiIVP8Szw4rInh66Ug4vK7hUP/XNW7mNlwnyigquD0yahoL M63Lui9KOX2JJfCS4aXoRSWbq2/sjWh6wG1i57WAGNrpfv+5LQnANF1FyIMWYkzl wX2ep5DFAqtJNxpp76CitgSC4QnhDDtvs9B/iNUiCA4jIoTzvfmZzHEzvVUb/aVX ZzYhJiehekht/TePvzKXMTcYAfvMoCicllPDgM0vCUDj0clMBEVd887gt3gxjoWZ TcRVLPlyMnV5nUbGbnJRpz5dIQXnkRvCU9Pm42zji+ty/atDF2brKVbQ37vVl20v LPJNifIzL2pC6U1w8NRjDkPHG8knWTMGFrwfPRETuCqC5W+Xv1Etfde3PQsvntiX IbEgtgRdIPvWNFWzC3wY2bLX3laNut5EbfjqAqDky/MxKAg1
=wqM8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Philippe (2024.08.16_00:52:25_+0000)

Now I do have some standalone python scripts for which it makes not
much sense to make them (Python) packages (i.e. there's no
__init__.py, etc.), yet I'd still like to have stuff like
automatically getting the right Debian package dependencies in a
Debian package.

Is that even intended to work with dh_python?

dh_python doesn't care what form your python package is in. It just
looks for the metadata in .dist-info / .egg-info.

So, if your package declares dependencies in in the packaging, and
installs correctly with python3-build, it'll work.

Stefano

--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Aug 16, 2024 at 11:02:18PM +0200, Philippe Cerfon wrote:

Hey again

On Fri, Aug 16, 2024 at 6:26 PM Philippe Cerfon <[email protected]> wrote:

Still I fail to understand, where that auto-completed my-script-file
comes from in ptpython.
Any ideas what I'm doing wrong?

Maybe it's not me doing something wrong.
I have:
ls -al /usr/bin/*.py

This is against the Policy 10.4 by the way: "When scripts are installed
into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently
used to implement it."


--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmbASM8tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh FrIP/0eh7lRRlJaEMm1P+wKnuBXYOk7phDw4vPE7W8LRfP8gDdaZRtStLCTXcV/Z IC6EMTUHHrMeI07/8jmONVQ6AGB+PphEtqudngKGHnkfzAiqAL26WZy6ZVOMWWNB FmsMc5wvEFqoONqKMV+l3wcpLVCLklmVlzhjtR7nZzG/bJ9Ren4W9m3JULyjDQJR 1OIA1CGjUNjYsnEpo/04gePHFgRLeIcDDEELL0apFj5gPOIyA+IiEAydptWmWFZT jTMEz3q2u32J3QsnuRfbv5WpmUwgu50j2ymevH3iuYiIVNLoxtiSX4XkQ2c2lmeS GVy5JYah5WXzOyJjBzPCL+gWE8+f2FidRNIeppe91G2Iq9JA8bt8V+8go9xcMhH4 O679aC+WX0e/kM3/iaPmq1f7RItWvkkIOI6PoxVay8sFJ9RXjFOsY0C/PG1ZP2Vv Y+iN17ItktwOGk4LT4k5gbWHGjJ+lli1OhHaKt8tqzjioaquQBcDZOVqi+/6WMZ5 90acOPe8SIF4qKetAUulXLGbsqbJIHrELgF/UDczezJjgwmrDm0g/VEUui4GMbVk aKUCQyNDFsCurS9uU9bqqRcVnBqbEDWdK5j60+HAnttJzvvqMuJANk7V0ryMvINx WfUp5ygeDOyyyAloM6QHwafzVNrmEJfKUWYvI5XP65r9KT8G
=yKy0
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)