richard boulton crxniebtartarusorg martin v löwis wrote numbers arent ridiculously large tried range231 pass 32bit laptop took 7368 seconds 12 bit minutes aside contrast range2311 pass took 1311 seconds looks like theres potential optimization theres always potential optimization question whether worth increased coding maintenance effort means optimization already implemented py iterrange2311 py iterrange231 iow iterate long ranges much slower per element iterating short range slow example given one returned items needs long possible optimisation would work well case would automatically split range two parts part needs short integers part needs longs mixedrange_iterator type returned items one followed items general case might need three subiterators used range232 232 example would decomposed range232 2311 range231 2311 range231 232 saying worth optimisation particularly im going guess lines grandparent poster thinking along richard _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom fri 08 aug 2008 071735 0100 python3000 range issues