ah i c
On Fri, Aug 21, 2015 at 11:08 PM, Maciej Fijalkowski
wrote:
> I don't think so, our 3.x releases are usually done at different times
>
> On Fri, Aug 21, 2015 at 4:07 PM, Phyo Arkar
> wrote:
> > Will there be any 3.x release included in this?
>
I don't think so, our 3.x releases are usually done at different times
On Fri, Aug 21, 2015 at 4:07 PM, Phyo Arkar wrote:
> Will there be any 3.x release included in this?
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/lis
Le 21/08/15 13:14, Vaibhav Sood a écrit :
Hi,
I am a newbie to pypy and looking to start making some contributions to
the project. I was looking at the buildbot test case failures (after
referring to an earlier thread on this forum:
https://mail.python.org/pipermail/pypy-dev/2015-July/013751.htm
Will there be any 3.x release included in this?
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
Hi,
I am a newbie to pypy and looking to start making some contributions to the
project. I was looking at the buildbot test case failures (after referring to
an earlier thread on this forum:
https://mail.python.org/pipermail/pypy-dev/2015-July/013751.html ) for the
py3.3 branch and to start of
Hi Matti,
On 21 August 2015 at 13:23, Matti Picus wrote:
> For some reason the "hg pull" command is doing so with a revision hash, as
> can be seen here
Ah, you mean that doing "hg pull --rev xxx" breaks the order of the
revisions. Indeed, it does...
Armin
On 20/08/15 13:07, Armin Rigo wrote:
Hi Matti,
It's likely
because it has custom commits in it that it is out-of-sync. If we
freshly clone from bitbucket, we always get the same revisions in the
same order, as far as I know.
A bientôt,
Armin.
For some reason the "hg pull" command is doing
