unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Cc: 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: Tue, 17 Dec 2024 14:26:32 +0100	[thread overview]
Message-ID: <87msguh247.fsf@elephly.net> (raw)
In-Reply-To: <87seqmheew.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 17 Dec 2024 10:00:55 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

> 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 upgraded the above packages, too.

> Unless anyone objects I'll destroy and recreate the python-team branch
> with my commits tonight.

I've pushed the branch.  Please add your fixes there.  Let's try to get
this merged soon.  The goal here is to reduce the number of recently
introduced build failures significantly.

-- 
Ricardo


  reply	other threads:[~2024-12-17 13:27 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 [this message]
2024-12-18  1:13 ` Maxim Cournoyer
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=87msguh247.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=lars@6xq.net \
    --cc=marius@gnu.org \
    --cc=me@bonfacemunyoki.com \
    --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).