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

2006-05-26 Thread Armin Rigo
Hi Bob, On Thu, May 25, 2006 at 10:58:21PM +, Bob Ippolito wrote: > Python ints are a heck of a lot faster to work with than Python longs > and have the additional benefit that psyco psyco.sourceforge.net> can optimize the hell out of int but can't do > anything at all for long. Alternat

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

2006-05-26 Thread Thomas Wouters
On 5/26/06, Tim Peters <[EMAIL PROTECTED]> 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 unbo

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

2006-05-25 Thread Tim Peters
[Bob Ippolito] > ... > Unfortunately, this change to the struct module slightly alters the > documented API for the following format codes: I, L, q, Q. Currently > it is documented that those format codes will always return longs, > regardless of their value. I view that more as having documented

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

2006-05-25 Thread Bob Ippolito
Python ints are a heck of a lot faster to work with than Python longs and have the additional benefit that psyco can optimize the hell out of int but can't do anything at all for long. This is important because psyco is currently in pretty wide-spread use amongst people who need to squeeze