From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Please migrate your distutils-r1 ebuilds to use PEP517 builds
Date: Sun, 10 Mar 2024 01:08:06 -0500 [thread overview]
Message-ID: <525e8af1-2958-40c3-ac15-f94029edf431@gmail.com> (raw)
In-Reply-To: <c26105b75a8fc5a085d649bac3059931d314f865.camel@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1689 bytes --]
On 3/9/24 9:32 AM, Michał Górny wrote:
> Hi,
>
> Please consider the "legacy" build mode to be strongly deprecated, both
> in distutils-r1 and upstream (to the point that sole presence of
> packages installed that way triggers deprecation warnings elsewhere,
> sigh). Therefore, if you haven't done that already, please look into
> converting your packages to use PEP517 builds (DISTUTILS_USE_PEP517,
> installing .dist-info rather than .egg*). We'd like to eventually
> remove the legacy code paths from the eclass, as they are not well-
> tested at this point, and they certainly are lacking, compared to
> the newer code paths.
Reminder as well to be *extremely* careful when looking at non-library
packages, since projects using setup.py as a "pythonic Makefile" run a
very high risk of being broken under PEP 517 (and this is unavoidable,
since the python wheel standard doesn't support application packaging,
only *.py libraries and executables).
As noted in the migration guide link, you MUST check the list of
installed files before and after switching and make sure the switch
doesn't break anything.
> This also applies to overlay maintainers, since overlays will be
> affected once we remove old code paths.
>
> The migration guide is here:
>
> https://projects.gentoo.org/python/guide/migration.html#migrating-to-pep-517-builds
>
> While at it, please also look at replacing `distutils_enable_tests
> setup.py` with one of the other test runners, as running `setup.py test`
> has been deprecated upstream as well. Or running `setup.py` at all, but
> the latter is less likely to suddenly stop working.
>
--
Eli Schwartz
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-10 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 14:32 [gentoo-dev] Please migrate your distutils-r1 ebuilds to use PEP517 builds Michał Górny
2024-03-10 6:08 ` Eli Schwartz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525e8af1-2958-40c3-ac15-f94029edf431@gmail.com \
--to=eschwartz93@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox