Hi Dino,
On Thu, Sep 1, 2011 at 7:07 PM, Dino Viehland wrote:
> Ahh yeah, I think I had some weird 1.5 build on my laptop where I tried it.
> Guess it's time to upgrade.
Same in 1.6, but I fixed it in "default" today.
Armin
___
pypy-dev mailing list
p
Antonio wrote:
> it seems to work fine with pypy 1.6. Note that str() is called twice for each
> line, so we get 1, 3, 5, 7..., but this happens only on cpython.
Ahh yeah, I think I had some weird 1.5 build on my laptop where I tried it.
Guess it's time to upgrade.
_
Hi,
On Thu, Sep 1, 2011 at 10:57 AM, Armin Rigo wrote:
> It works as expected on CPython 2.7. Is it a bug? :-)
Fixed in 414bb2d98b0c.
Armin
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
On 01/09/11 10:57, Armin Rigo wrote:
Hi,
On Thu, Sep 1, 2011 at 9:58 AM, Antonio Cuni wrote:
it seems to work fine with pypy 1.6. Note that str() is called twice for
each line, so we get 1, 3, 5, 7..., but this happens only on cpython.
...but this happens only on PyPy, you mean. It works a
Hi,
On Thu, Sep 1, 2011 at 9:58 AM, Antonio Cuni wrote:
> it seems to work fine with pypy 1.6. Note that str() is called twice for
> each line, so we get 1, 3, 5, 7..., but this happens only on cpython.
...but this happens only on PyPy, you mean. It works as expected on
CPython 2.7. Is it a b
On 01/09/11 05:28, Dino Viehland wrote:
This came up on an internal discussion, I thought it was fun, especially given
that we all behave differently:
Paste this into the REPL:
[cut]
it seems to work fine with pypy 1.6. Note that str() is called twice for each
line, so we get 1, 3, 5, 7...,
