On 04/01/2011 16:54, Barry Warsaw wrote: > On Jan 04, 2011, at 10:21 AM, Alex Gaynor wrote: > >> Ugh, I can't be the only one who finds these special cases to be a little >> nasty? >> >> Special cases aren't special enough to break the rules. > Yeah, I agree. Still it would be interesting to see what kind of performance > improvement this would result in. That seems to be the only way to decide > whether the cost is worth the benefit. > > Outside of testing, I do agree that most of the builtins could be pretty > safely optimized (even open()). There needs to be a way to stop all > optimizations for testing purposes. Perhaps a sys variable, plus command line > option and/or environment variable? Although testing in an environment deliberately different from production is a recipe for hard to diagnose bugs. Michael > -Barry > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110104/f79a65d5/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4