From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, lars@6xq.net, marius@gnu.org,
me@bonfacemunyoki.com, sharlatanus@gmail.com,
tanguy@bioneland.org, jgart@dismail.de
Subject: Re: python-team: New branch
Date: Wed, 18 Dec 2024 10:13:45 +0900 [thread overview]
Message-ID: <874j31sshi.fsf@gmail.com> (raw)
In-Reply-To: <87seqmheew.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 17 Dec 2024 10:00:55 +0100")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Guix,
>
> I'm CC'ing the python-team.
>
> Since the merge of the python-team branch we've seen a bunch of
> new build failures to popular packages. I've started work to repair
> some of the damage.
>
> I think we should start a new python-team branch where we build out
> important upgrades and fixes. I'd like to aim for merging that new
> branch before the end of the year, so let's try to restrict ourselves to
> important fixes only.
>
> If there is more time we should also consider upgrading these packages:
>
> python-typing-extensions
> python-virtualenv
> python-platformdirs
> python-colorama
> python-chardet
>
> (I patched out version checks in python-tox to avoid upgrading, but I
> think we should not do that habitually.)
I have a Python mass update branch I've been developing, holding it back
because I kept finding breakage (whether caused by my changes or
already there). There's now 200 commits in it, including an update to
virtualenv and typing extensions, along Python build systems
improvements.
I'll try getting it a bit further in terms of packages breakage then
send it for review. If you'd rather see it already and work on a
wip-python-team branch, I could submit it already in its more rough
form.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-12-18 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 9:00 python-team: New branch Ricardo Wurmus
2024-12-17 13:26 ` Ricardo Wurmus
2024-12-18 1:13 ` Maxim Cournoyer [this message]
2024-12-18 7:52 ` Ricardo Wurmus
2024-12-19 2:30 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2024-12-17 15:17 Sharlatan Hellseher
2024-12-17 16:53 ` Ricardo Wurmus
2024-12-21 20:33 ` Ricardo Wurmus
2024-12-21 20:43 ` Sharlatan Hellseher
2024-12-22 11:29 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874j31sshi.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=rekado@elephly.net \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).