Hi Simon,
On Mon, May 6, 2013 at 12:48 AM, Simon Cross wrote:
> I was thinking along similar signs -- we could ask for things like "x
> is ''" or "x is 3" to be added to PEP8 (I think any use of "is" with a
> constant on one or more sides is likely suspect).
That may be a good idea. If the comp
Hi Michael,
On Sun, May 5, 2013 at 10:40 PM, Michael Hudson-Doyle wrote:
> I want to say something about negative zeroes here
Right: on floats it's not actually the usual equality, but equality of
the bit pattern (using float2longlong).
A bientôt,
Armin.
__
I was thinking along similar signs -- we could ask for things like "x
is ''" or "x is 3" to be added to PEP8 (I think any use of "is" with a
constant on one or more sides is likely suspect).
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python
I wonder if maybe we can't have some sort of flag to add extra
compatibility warnings, and then have a warning when `is` is used ints,
strings, etc?
Alex
On Sun, May 5, 2013 at 3:43 PM, Simon Cross wrote:
> Solution 3 sounds bad since it breaks things in PyPy for people who
> were using "is" m
Solution 3 sounds bad since it breaks things in PyPy for people who
were using "is" more correctly in CPython.
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Personally, I think that being implementation detail compatible with CPython
is the way tio go if we want to achieve maximum popularity in the short run.
Making a sane implementation (Armins third option) is the one that I think
will serve the Python community in the best way in the long run. Us
On 5 May 2013 21:59, Armin Rigo wrote:
> Hi all,
>
> I'm just wondering again about some "bug" reports that are not bugs,
> about people misusing "is" to compare two immutable objects. The
> current situation in PyPy is that "is" works like "==" for ints,
> longs, floats or complexes.
>
I want
On Sun, May 5, 2013 at 12:59 PM, Armin Rigo wrote:
>
> Can we fix it once and for all? It's annoying because of id: if we
> want ``x is y`` for equal huge strings x and y, but still want
> ``id(x)==id(y)``, then we have to compute ``id(some_string)`` in a
> rather slow way, producing a huge numb
Hi all,
On Sun, May 5, 2013 at 9:16 PM, Steven D'Aprano wrote:
>> It's true what you're saying, but we consistently see bug reports
>> about people comparing ints or strings with is and complaining that
>> they work fine on cpython, but not on pypy.
>
> Then their code is buggy, not PyPy. But you
Hi Amaury,
On Sun, May 5, 2013 at 1:38 PM, Amaury Forgeot d'Arc wrote:
> Strings are not always cached; with CPython2.7:
x = u'é'.encode('ascii', 'ignore')
x == '', x is ''
> (True, False)
That's true, there are such cases, but that's partially irrelevant for
this issue: strings that *
On 06/05/13 03:35, Maciej Fijalkowski wrote:
On Sun, May 5, 2013 at 1:20 PM, Steven D'Aprano wrote:
On 05/05/13 19:59, Armin Rigo wrote:
Hi all,
I'm just wondering again about some "bug" reports that are not bugs,
about people misusing "is" to compare two immutable objects. The
current situ
On Sun, May 5, 2013 at 1:20 PM, Steven D'Aprano wrote:
> On 05/05/13 19:59, Armin Rigo wrote:
>>
>> Hi all,
>>
>> I'm just wondering again about some "bug" reports that are not bugs,
>> about people misusing "is" to compare two immutable objects. The
>> current situation in PyPy is that "is" work
Hi,
2013/5/5 Armin Rigo
> Hi all,
>
> I'm just wondering again about some "bug" reports that are not bugs,
> about people misusing "is" to compare two immutable objects. The
> current situation in PyPy is that "is" works like "==" for ints,
> longs, floats or complexes. It does not for strs or
On 05/05/13 19:59, Armin Rigo wrote:
Hi all,
I'm just wondering again about some "bug" reports that are not bugs,
about people misusing "is" to compare two immutable objects. The
current situation in PyPy is that "is" works like "==" for ints,
longs, floats or complexes. It does not for strs o
Hi all,
I'm just wondering again about some "bug" reports that are not bugs,
about people misusing "is" to compare two immutable objects. The
current situation in PyPy is that "is" works like "==" for ints,
longs, floats or complexes. It does not for strs or unicodes or
tuples. Now of course so
Hi,
On Sun, May 5, 2013 at 11:12 AM, Maciej Fijalkowski wrote:
>> Doesn't PyPy have a "compile to binary" option? I thought it did, but I
>> may be mistaken.
>
> It does not.
It does, in a way, but it's not an option available for the user on a
single function at a time. The confusion comes fro
> Doesn't PyPy have a "compile to binary" option? I thought it did, but I
> may be mistaken.
It does not.
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
17 matches
Mail list logo
