unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vincent Prat <vprat@deeplinks.com>
Cc: 64189@debbugs.gnu.org
Subject: [bug#64189] [PATCH] gnu: python-pyflakes: Update to 3.0.1.
Date: Thu, 07 Sep 2023 09:13:04 -0400	[thread overview]
Message-ID: <8734zqnn33.fsf@gmail.com> (raw)
In-Reply-To: <CAH9Ak7+YCjXnBD6QBa4yV4+gdU=kN+95U1FNV1Nx1kciQwcE_Q@mail.gmail.com> (Vincent Prat's message of "Thu, 7 Sep 2023 13:52:39 +0200")

Hi,

Vincent Prat <vprat@deeplinks.com> writes:

> Hi,
>
> Obviously, version 3 of python-pyflakes introduced some breaking changes.
> I guess that most of these build failures are due to other packages
> not being up-to-date.
> For instance, some of them can be fixed by updating python-flake8
> (https://github.com/PyCQA/pyflakes/pull/751) and python-pylama
> (https://github.com/PyCQA/pyflakes/issues/721).
>
> What is the procedure in such a case?

Since Python doesn't support mixed versions, at least for libraries,
this implies that the complete Python distribution in Guix must be
updated to work with the new version.  That may sounds bad, but as you
pointed, it typically involves upgrading the packages broken post
update, which shouldn't be too difficult (but is time consuming).

guix refresh --upgrade and etc/committer.scm are your friends here.

Since the number of rebuilds is a bit large for master, a dedicated
branch could be created (or the python-team branch reused) to build and
QA the new work.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-09-07 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20  9:21 [bug#64189] [PATCH] gnu: python-pyflakes: Update to 3.0.1 Vincent Prat
2023-09-06 14:25 ` Maxim Cournoyer
2023-09-07 11:52   ` Vincent Prat
2023-09-07 13:13     ` Maxim Cournoyer [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

  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=8734zqnn33.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=64189@debbugs.gnu.org \
    --cc=vprat@deeplinks.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 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).