RetroSearch Browse

Sat Jun 18 11:06:34 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-June/054317.html

Guido van Rossum wrote:

>On 6/17/05, Raymond Hettinger <raymond.hettinger at verizon.net> wrote:
>  
>
>>IIRC, there was a decision to not implement phase C and to keep the
>>trailing L in representations of long integers.
>>    
>>
>
>Actually, the PEP says phase C will be implemented in Python 3.0 and
>that's still my plan.
>
>  
>
>>If so, I believe the PEP can be marked as final.  We've done all we're
>>going to do.
>>    
>>
>
>For 2.x, yes. I'm fine with marking it as Final and adding this to PEP
>3000 instead.
>
>  
>
I am very concernced about something. The following code breaks with 2.4.1:

fcntl.ioctl(self.rtc_fd, RTC_RD_TIME, ...)

Where RTC_RD_TIME = 2149871625L

In Python 2.3 it is -2145095671.

Actually, this is supposed to be an unsigned int, and it was construced
with hex values and shifts.

Now, with the integer unification, how is ioctl() supposed to work? I
cannot figure out how to make it work in this case.

I suppose the best thing is to introduce an "unsignedint" type for this
purpose. As it is right now, I cannot use 2.4 at all.

-- 

-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Keith Dart <kdart at kdart.com>
   public key: ID: F3D288E4
   =====================================================================

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdart.vcf
Type: text/x-vcard
Size: 179 bytes
Desc: not available
Url : http://mail.python.org/pipermail/python-dev/attachments/20050618/ec966cbe/kdart.vcf

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-June/054317.html below:

[Python-Dev] Is PEP 237 final -- Unifying Long Integers and Integers