Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Andrey Rahmatullin Newsgroups: linux.debian.maint.python Subject: Re: How do you create entry-points for Python applications? Date: Mon, 19 Dec 2022 14:40:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Dec 19 13:31:19 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 X-Greylist: delayed 1402 seconds by postgrey-1.36 at bendel; Mon, 19 Dec 2022 13:31:01 UTC MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="o+qXL5FMGSyDlOs9" Content-Disposition: inline X-Mailing-List: archive/latest/20620 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Y6BiF4olQSi2UZ62@belkar.wrar.name Approved: robomod@news.nic.it Lines: 55 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 19 Dec 2022 18:07:35 +0500 X-Original-Message-ID: X-Original-References: <385ec8ae34ef53f01a86b49c0f15504f@posteo.de> Xref: csiph.com linux.debian.maint.python:14753 --o+qXL5FMGSyDlOs9 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 18, 2022 at 07:18:44PM +0000, c.buhtz@posteo.jp wrote: > Hello, > a python application isn't a binary but a script. So to invoke such an > application there need to be a shell script somewhere in PATH that invoke > that script via python3 interpreter. Imagine an application with a GUI (q= t, > tikinter, gtk, ...). >=20 > On the upstream site modern python projects using pyproject.toml (only), > some use setup.cfg. > There you can define "entry points" and the "pip" installer does generate= a > shell script based on that information and place it in PATH. > That is a nice mechanism when installing via pip. >=20 > On your site as distro maintainers. How do you take care of then when > creating deb files? I feel like this question is not really specific to pyproject.toml etc.: entry points are an old concept and we have a lot of packages shipping setuptools entry points (grep your /usr/bin for "load_entry_point"). For these packages the executable is indeed created automatically by the packaging tools, and I would expect the same to happen for any other supported setuptools replacement. --=20 WBR, wRAR --o+qXL5FMGSyDlOs9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmOgYhMtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 2mQP/jzixv3IfFTsPOoYXQimfF7iY2ilxPmbs2je5PVoRoGMQOXkUIScD2u5Tnks NzZZARhSQIPpYQqPfiBBl4hJ/oiz8s0G12dBV9c5vTDkK8/aSAJG7gHA38J/JU8U XlT4Cl9e4Ls04PAKIw0+eWyhIQfUO6irB8TZFg52JNfIYYGIELWyyB7/LARUa1sh Wj7IoAih22uzjloM7m+96WkfjRc/xhf3KAyp7ELW3kTzVUK/K9/BgCTMSipKICDO V7vkuQuvQ2SwUGvQLQyrqac2IkQD/Ux0g/P9RE5Ma1S6YV67trOrceNJcQKhv6cG MUWbeVbbT/mZ4QfH1Th/CJkgdeM6tYDZv2McZlashMKgZbgU7Ywkwm2KDJq2uYQe fz7MYWidKe0lF0PxlxyFxE/ZbC1ruVAIbPi8JnYjiCTdXbF4PYQzixiShEUxYNmK nTE/z2FtTqfsoisdRWDZz3hPpqvNg/fZ/YaaSd3TbSBbUz47mA+GqLG6Ie3NgNsx IDF4daWFVc4k5E4JCbLVdYYqU57X5xwHjmZACOMpux6e5MDHunXaQ0pHfeBWoRVY T+BFKlY04iqWKTzXrHjiu8Wwge/xqWySjW9gkkofh4/wNNAj2MdbZvlmKnElm9zc EO7j15JI4UQS9XCNXo/DDFQKbvcxXKLEGaBUw7fSHtG9BrXG =o3G8 -----END PGP SIGNATURE----- --o+qXL5FMGSyDlOs9--