On 25/11/2011 15:48, Paul Moore wrote: > On 25 November 2011 15:07, Amaury Forgeot d'Arc<amauryfa at gmail.com> wrote: >> 2011/11/25 Paul Moore<p.f.moore at gmail.com> >>> It would be nice to have the optimisation back if it's easy enough to >>> do so, for quick-and-dirty code, but it is not a good idea to rely on >>> it (and it's especially unwise to base benchmarks on it working :-)) >> Note that this string optimization hack is still present in Python 3, >> but it now acts on *unicode* strings, not bytes. > Ah, yes. That makes sense. Although for concatenating immutable bytes presumably the same hack would be *possible*. Michael > Paul > _______________________________________________ > 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
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