Armin Rigo wrote:
If it is really 0.5%, then we're fine. Just remember that PyStone is an amazingly uninformative and crappy benchmark.Hi Raymond, On Mon, May 29, 2006 at 02:02:25PM -0700, Raymond Hettinger wrote:Please run some better benchmarks and do more extensive assessments on the performance impact.At the moment, I'm trying to, but 2.5 HEAD keeps failing mysteriously on the tests I try to time, and even going into an infinite loop consuming all my memory - since the NFS sprint. Am I allowed to be grumpy here, and repeat that speed should not be used to justify bugs? I'm proposing a bug fix, I honestly don't care about 0.5% of speed. The "justify bugs" terminology is pejorative and inaccurate. It is clear that the current dict behavior was a concious design decision and documented as such. Perhaps the decision sucked and should be changed, but it is not a bug. and I consider myself an everyday Python user, Something may have been lost in translation. Using it every day is not the same as being an everyday user ;-) There is no doubt that you routinely stress the language in ways ways that are not at all commonplace. All I'm asking is that there be a well thought-out assessment of whether the original design decision was struck the appropriate balance between practicality Raymond |
_______________________________________________ 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