Groups > comp.lang.python > #19332

Re: String interning in Python 3 - missing or moved?

References	<CAPTjJmr5=8H9pmWMQ1Q==O1DFGe31ykOBXNzQ9YhS+W8aaAxfw@mail.gmail.com> <CAMZYqRQXfLTrwzqma=ryVKmJByzPtfQqQRa8OjGG7d+qZ7KNGA@mail.gmail.com> <jflbf2$l09$1@dough.gmane.org> <CAPTjJmrYgnYXstkdiN9T1ReV9KxjWN+wsmNita_oz4W_KzX78A@mail.gmail.com> <jflpds$2o8$1@dough.gmane.org>
Date	2012-01-24 00:33 -0800
Subject	Re: String interning in Python 3 - missing or moved?
From	Chris Rebert <clp2@rebertia.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.5021.1327394031.27778.python-list@python.org> (permalink)

Show all headers | View raw

On Tue, Jan 24, 2012 at 12:17 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
> Chris Angelico, 24.01.2012 05:47:
>> Lua and Pike both quite happily solved hash collision attacks in their
>> interning of strings by randomizing the hash used, because there's no
>> way to rely on it. Presumably (based on the intern() docs) Python can
>> do the same, if you explicitly intern your strings first. Is it worth
>> recommending that people do this with anything that is
>> client-provided, and then simply randomize the intern() hash?
>
> If you want to encourage them to fill up their memory with user provided
> data in a non-erasable way,

Actually, quoth intern()'s docs:
"Interned strings are not immortal; you must keep a reference to the
return value of intern() around to benefit from it."

Cheers,
Chris

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: String interning in Python 3 - missing or moved? Chris Rebert <clp2@rebertia.com> - 2012-01-24 00:33 -0800

csiph-web