all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: 46848@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#46848] [PATCHES] [core-updates] PEP 517 python-build-system
Date: Wed, 5 Jan 2022 15:51:29 +0100	[thread overview]
Message-ID: <YdWwcWM5I+zJW8tU@noor.fritz.box> (raw)
In-Reply-To: <YbeomE4Q02bPiPM+@noor.fritz.box>

Hi everyone,

I pushed the 3rd version of my new PEP 517-based python-build-system
into wip-python-pep517. I removed the dependency on python-pypa-build
for building packages and instead implemented building with a single
python invokation. This simplifies bootstrapping Python. The 'install
phase also learned how to create scripts in bin/ from an entry points
specification.

Currently 600 of 2212 packages using python-build-system are failing to
build. That’s alot, but most failures so far were related to testsuites,
which were not enabled correctly previously because 'check was not
replaced manually. And some fail because upstream does not separate
sources and tests and a name clash occurs. This also happens when C
extensions are build and there does not seem to be a workaround.

This number does not include Python 2 packages, which will probably
break with this new build system. Since Python 2 is EOL anyway I suggest
to entirely remove Python 2 support before merging this changeset. After
merging we should upgrade the entire Python ecosystem, because alot of
packages are already years old.

Cheers,
Lars

PS: Maxim: This is your ping for a review (via #52269). Thanks :)





  reply	other threads:[~2022-01-05 14:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 13:43 [bug#46848] [PATCHES] [core-updates] PEP 517 python-build-system Lars-Dominik Braun
2021-05-15  9:31 ` Lars-Dominik Braun
2021-12-13 20:10   ` Lars-Dominik Braun
2022-01-05 14:51     ` Lars-Dominik Braun [this message]
2022-01-20 15:41       ` Marius Bakke
2022-01-20 18:43         ` Lars-Dominik Braun
2022-01-20 20:43           ` Marius Bakke
2023-01-11 15:41             ` Maxim Cournoyer
2023-02-10 10:13               ` bug#46848: " Lars-Dominik Braun
2022-02-26 14:10           ` [bug#46848] " Maxim Cournoyer
2022-02-28 19:25             ` Lars-Dominik Braun
2022-02-28 22:32               ` Maxim Cournoyer
2022-04-24  9:13             ` Lars-Dominik Braun
2022-04-24  9:22               ` Lars-Dominik Braun
2022-01-23  5:29 ` Maxim Cournoyer
2022-01-23 10:21   ` Lars-Dominik Braun

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=YdWwcWM5I+zJW8tU@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=46848@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.