Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #59213 > unrolled thread

Re: 'isimmutable' and 'ImmutableNester'

Started byrandom832@fastmail.us
First post2013-11-12 10:48 -0500
Last post2013-11-12 10:48 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: 'isimmutable' and 'ImmutableNester' random832@fastmail.us - 2013-11-12 10:48 -0500

#59213 — Re: 'isimmutable' and 'ImmutableNester'

Fromrandom832@fastmail.us
Date2013-11-12 10:48 -0500
SubjectRe: 'isimmutable' and 'ImmutableNester'
Message-ID<mailman.2474.1384271901.18130.python-list@python.org>
On Tue, Nov 12, 2013, at 4:39, Frank-Rene Schäfer wrote:
> > All you've done is proven that you can subvert things. By fiddling
> > with __hash__, __eq__, and so on, you can make sets and dicts behave
> > very oddly. Means nothing.
> 
> To the contrary, it means everything about what 'isimmutable' could
> contribute: security against advert or inadvert insertion of mutable
> objects.

If an object can lie about its hashability, it can lie to your function
too... unless you don't intend to provide a way for a _genuinely_
immutable class to say so.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web