On Fri, Feb 22, 2008, Andrew MacIntyre wrote: > Vladimir Marangozov wrote: >> >> And, of course, if the int/float freelist scheme was a real issue >> we would have probably heard of it by now in a very sound way. > > Not much noise has been made here, but I've come across 2 separate > complaints in different mailing lists in the last month (one of the > complainants had some hope that gc.collect() might help...) Is it a > deafening roar? No, but I doubt the volume will do anything but > increase...
Actually, it's a regular issue that crops up on c.l.py, but almost always in the context of range(bignum). Because there's an easy workaround and Python 3.0 changes the semantics of range(), there hasn't been much clamor to fix it. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "All problems in computer science can be solved by another level of indirection." --Butler Lampson _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
