4 ms·
Most likely the biggest cause is the removal of special-casing for small integers. http://docs.python.org/dev/3.0/whatsnew/3.0.html#performance http://docs.pyt
by kaens 18y ago
Most likely the biggest cause is the removal of special-casing for small integers.
http://docs.python.org/dev/3.0/whatsnew/3.0.html#performance http://docs.python.org/dev/3.0/whatsnew/3.0.html#performance
I'm anticipating a more thorough discussion of this on python-list or python-dev in the near future.
- petercooper 18y agoI expect it's just a case of removing optimizations in order to get everything stable, then they can start work on new optimizations. I'm not a Python dev though, so elaboration would be cool ;-)
- kaens 18y agoIn this particular case, I think it's because all ints are now longs. Or rather, there's one int type and it behaves like a long. I'm not a python dev either, but that's what I've gathered by lurking the python-dev and python-3000 mailing lists.
- cpr 18y agoJust to clarify for non-Pythonistas, a "long" is an unlimited precision integer.