On Wed, Mar 27, 2013 at 7:04 PM, Armin Rigo wrote:
>> How is the state of the STM branch? Just a POC or Armin has a idea for
>> producing a new version of PyPy?
>
> What is "POC"?
Sorry, "proof of concept". I surprised to not see STM in the list.
--
S
On Sat, Mar 23, 2013 at 10:58 PM, Alex Gaynor wrote:
> If you've got an idea, or are interested in mentoring you should add
> yourself/the idea.
How is the state of the STM branch? Just a POC or Armin has a idea for
producing a new version of PyPy?
--
Sebastien Douche
Twitter: @
Both backend have the full DAG.
--
Sebastien Douche
Twitter: @sdouche / G+: +sdouche
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
fe: no new version, even for major bugs.
--
Sebastien Douche
Twitter: @sdouche / G+: +sdouche
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
man/man1/python2.7.1.gz
pypy1.6:
/usr/bin/pypy
/usr/share/man/man1/pypy.1.gz
As Maciej said, it's a first step (and a good one!).
--
Sebastien Douche
Twitter : @sdouche
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
ges (am I
wrong?).
--
Sebastien Douche
Twitter : @sdouche
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
sure to understand, with Git you know easily new commits since last fetch :
git log origin/master..master
Same command as :
git log master ^origin/master (a and not b).
I think it's the same thing with hg (minus inclusion/exclusion
limits). I'm wrong?
-
be to use bitbucket for the day to day job, and push
on python.org regularly (each release?). The cost is very low.
--
Sebastien Douche
Twitter : @sdouche
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
