RetroSearch Browse

Fri May 26 12:32:20 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-May/065213.html

On 5/26/06, Tim Peters <tim.peters at gmail.com> wrote:
>
> [Bob Ippolito]
> > Given the interchangeability of int and
> > long, I don't foresee any other complications with this change.
> >
> > Thoughts?
>
> +1, and for 2.5.  Even int() doesn't always return an int anymore, and
> it's just stupid to bear the burden of an unbounded long when it's not
> really needed.

Completely agreed. We've been unifying longs and integers for whole
releases, I cannot imagine anyone not getting the hint. Ints and longs are
the same thing, deal with it. Whether you get an int or a long for a
particular value is a platform-dependant accident anyway (people seem to be
ignoring 64-bit hardware all the time... I know Tim does :)

-- 
Thomas Wouters <thomas at python.org>

Hi! I'm a .signature virus! copy me into your .signature file to help me
spread!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20060526/09bbfbf0/attachment.htm 

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-May/065213.html below:

[Python-Dev] Returning int instead of long from struct when possible for performance