From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] Add new pytest for special cases
Date: Mon, 31 Oct 2016 13:20:02 -0400 [thread overview]
Message-ID: <20161031172002.GA31367@jasmine> (raw)
In-Reply-To: <877f8okh9w.fsf@elephly.net>
On Mon, Oct 31, 2016 at 10:19:07AM +0100, Ricardo Wurmus wrote:
> Leo Famulari <leo@famulari.name> writes:
> > I'd really prefer to run the Borg tests, so I want to add a newer
> > release of pytest and use it with Borg.
> >
> > I've been testing pytest upgrades locally, and there is some breakage,
> > so I think we should not try to upgrade it for all packages in this
> > core-updates cycle. Instead, I want to build on Hartmut's
> > wip-python-build-system to upgrade the core Python packages after this
> > core-updates cycle.
> >
> > WDYT?
>
> This makes sense. I looked over the patches and they look good to me.
>
> We have a lot of Python packages that really should be updated. We need
> some Python champions to take care of continued updates there.
Please check out Hartmut's wip-python-build-system branch :) I read
through the commits a couple days ago, and the general idea seems
reasonable, although I don't understand everything yet.
If we decide to continue with that approach, I will help upgrade the
core Python packages on top of it.
If not, I'll recreate the old wip-python branch after this core-updates
cycle is merged; I wanted to wait for Python 3.5 before continuing.
next prev parent reply other threads:[~2016-10-31 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 22:48 [PATCH 0/2] Add new pytest for special cases Leo Famulari
2016-10-30 22:48 ` [PATCH 1/2] gnu: Add python-pytest-2.9.2 Leo Famulari
2016-11-03 13:36 ` Ludovic Courtès
2016-10-30 22:48 ` [PATCH 2/2] gnu: borg: Run the tests with python-pytest-2.9.2 Leo Famulari
2016-11-03 13:36 ` Ludovic Courtès
2016-10-31 9:19 ` [PATCH 0/2] Add new pytest for special cases Ricardo Wurmus
2016-10-31 17:20 ` Leo Famulari [this message]
2016-11-02 17:35 ` Hartmut Goebel
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=20161031172002.GA31367@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.