Case Vanhorsen, 20.12.2009 01:38:
When I ported gmpy (Python to GMP multiple precision library) to
Python 3.x, I began to use PyLong_AsLongAndOverflow frequently. I
found the code to slightly faster and cleaner than using PyLong_AsLong
and checking for overflow.
You might want to look at the co
> On Mon, Dec 28, 2009 at 1:15 AM, Tarek Ziade wrote:
>
> This new operator removes the ambiguity the original proposal had,
> without making it more
> complex for common use cases. So if you dislike it, you will need to
> propose something
> else that also fixes the ambiguity we had.
Ok.
> Env
David Lyon wrote:
On Mon, Dec 28, 2009 at 1:15 AM, Tarek Ziade wrote:
This new operator removes the ambiguity the original proposal had,
without making it more
complex for common use cases. So if you dislike it, you will need to
propose something
else that also fixes the ambiguity we had.
Ok.
>> Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
>
> Requires-Dist: [Windows] pywin32 1.0+
>
> That's simpler, shorter, and less ambiguous. Easier to
> parse for package managers.
Don't you want the PEP to complete? Why this bike-shedding?
I can agree it's shorter. I can't agree that
On Jan 3, 2010, at 7:21 PM, Martin v. Löwis wrote:
>>> Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
>>
>> Requires-Dist: [Windows] pywin32 1.0+
>>
>> That's simpler, shorter, and less ambiguous. Easier to
>> parse for package managers.
>
> Don't you want the PEP to complete? Why thi
Hi Martin, Happy New Year,
>>> Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
>>
>> Requires-Dist: [Windows] pywin32 1.0+
>>
>> That's simpler, shorter, and less ambiguous. Easier to
>> parse for package managers.
>
> Don't you want the PEP to complete? Why this bike-shedding?
Well, I'