On Sat, Jul 02, 2016 at 09:10:12PM -0400, Leo Famulari wrote:
> The latest version of python-cryptography requires python-pytest >= 2.9 
> [0]. So, this patch series updates pytest, and fixes the breakage I was 
> able to find.
> 
> I tested most of the packages that use pytest, but not all of the 
> scientific / statistical computing packages, because they take forever
> to build. This is how I found the issues with virtualenv, pip, and 
> scripttest.
> 
> This release of pytest exits with an error if it can't find a test suite
> to run. So, we disable the check phases of virtualenv, pip, and 
> scripttest, because their test suites are not distributed via PyPi. If
> we want to run their test suites, we should package a source code
> snapshot instead of building from the release tarballs.
> 
> Pytest-runner must be updated to use the new pytest.
> 
> "Building the following 77 packages would ensure 210 dependent packages
> are rebuilt"...
> 
> [0]
> https://github.com/pyca/cryptography/issues/3034
> 
> Leo Famulari (6):
>   gnu: python-virtualenv: Disable tests.
>   gnu: python-pip: Disable tests.
>   gnu: python-scripttest: Disable tests.
>   gnu: python-pytest: Update to 2.9.2.
>   gnu: python-pytest-runner: Update to 2.8.
>   gnu: python-cryptopgraphy: Update to 1.4.
> 
>  gnu/packages/python.scm | 43 +++++++++++++++++--------------------------
>  1 file changed, 17 insertions(+), 26 deletions(-)
> 
> -- 
> 2.9.0
> 
> 

The patch-set looks good to me. For the curious, I checked python-pytest
and python2-pytest and ended up with 81 packages and 235 dependants, but
some of those are from my WIP tree in GUIX_PACKAGE_PATH

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted