<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 29, 2012, at 1:08 PM, Paul Moore wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">As it stands, I don't find the PEP compelling. The hardening use case<br>might be significant but Victor needs to spell it out if it's to make<br>a difference.</span></blockquote></div><br><div>If his sandboxing project needs it, the type need not be public.</div><div>It can join dictproxy and structseq in our toolkit of internal types.</div><div><br></div><div>Adding frozendict() as a new public type is unnecessary</div><div>and undesirable -- a proliferation of types makes it harder to</div><div>decide which tool is the most appropriate for a given problem.</div><div>The itertools module ran into the issue early. Adding a new </div><div>itertool tends to make the whole module harder to figure-out.</div><div><br></div><div><br></div><div>Raymond</div><div><br></div><div>P.S ISTM that lately Python is growing fatter without growing more</div><div>powerful or expressive. Generators, context managers, and decorators</div><div>were honking good ideas -- we need more of those rather than</div><div>minor variations on things we already have.</div><div><br></div><div>Plz forgive the typos -- I'm typing with one hand -- the other is holding</div><div>a squiggling baby :-)</div></body></html>