From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/2] Add new pytest for special cases
Date: Sun, 30 Oct 2016 18:48:01 -0400 [thread overview]
Message-ID: <cover.1477867669.git.leo@famulari.name> (raw)
We package version 2.7.3 of pytest, which was released in September
2015. I guess that Python development moves very quickly, because there
are already some packages whose test suites require a newer version of
pytest.
Notably, the most recent release of Borg, 1.0.8, requires something
called 'tmpdir_factory', which was introduced in pytest 2.8 [0]. You can
see this by building Borg on core-updates, where Python 3.5 makes the
test suite run (it never ran on master with Python 3.4).
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?
[0]
https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst#280
Leo Famulari (2):
gnu: Add python-pytest-2.9.2.
gnu: borg: Run the tests with python-pytest-2.9.2.
gnu/packages/backup.scm | 4 +++-
gnu/packages/python.scm | 25 +++++++++++++++++++++++++
2 files changed, 28 insertions(+), 1 deletion(-)
--
2.10.2
next reply other threads:[~2016-10-30 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 22:48 Leo Famulari [this message]
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
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=cover.1477867669.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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 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.