On Mon, Jul 11, 2016 at 11:50:47AM -0400, Leo Famulari wrote:
> On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote:
> > The ‘python-updates’ branch would seem right to me.
>
> The brand new python-updates branch is now ready for more Python-related
> commits!
I forgot to sign these c
On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote:
> The ‘python-updates’ branch would seem right to me.
The brand new python-updates branch is now ready for more Python-related
commits!
Leo Famulari skribis:
> On Sun, Jul 03, 2016 at 08:58:39AM +0300, Efraim Flashner wrote:
>> 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_PA
On Sun, Jul 03, 2016 at 04:15:17PM -0400, Leo Famulari wrote:
> On Sun, Jul 03, 2016 at 08:58:39AM +0300, Efraim Flashner wrote:
> > 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 thos
On Sun, Jul 03, 2016 at 08:58:39AM +0300, Efraim Flashner wrote:
> 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
What branch should it go
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
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
