[ python-Bugs-1607061 ] Incorrect use of 'int' and 'long' descriptions

[SourceForge.net]

Bugs item #1607061, was opened at 2006-12-01 19:22
Message generated for change (Comment added) made by gbrandl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1607061&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.5
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: John (johnjsal)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect use of 'int' and 'long' descriptions

Initial Comment:
On the main page for the array module, the following is in the type code chart:

'I' unsigned int     long     2
'l' signed long      int      4

Should 'long' and 'int' be switched in the second column?

Thanks,
John

----------------------------------------------------------------------

>Comment By: Georg Brandl (gbrandl)
Date: 2006-12-01 19:40

Message:
Logged In: YES 
user_id=849994
Originator: NO

No, the second column refers to the Python type used. This is "int" for
signed longs, because this is the base type for a Python int, and "long"
for unsigned ints, because on most 32-bit platforms int == long and
therefore an unsigned int is outside the range of a Python int.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1607061&group_id=5470