[Python-3000] Py3k release schedule worries
Georg Brandl
g.brandl at gmx.net
Tue Dec 19 20:02:05 CET 2006
More information about the Python-3000 mailing list
Tue Dec 19 20:02:05 CET 2006
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Barry Warsaw schrieb: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Dec 19, 2006, at 1:03 PM, Guido van Rossum wrote: > >> On 12/19/06, Fredrik Lundh <fredrik at pythonware.com> wrote: >>> Georg Brandl wrote: >>> >>>> so what about id() and intern(). Care to pronounce? >>> >>> moving/removing id()? please don't do that; id(obj) and type(obj) >>> are >>> essential tools for learning object semantics, and should be >>> trivial to >>> access and use. >> >> Right. I tend to agree with Fredrik about id(). I'm not so sure about >> intern() -- IMO its use is rare enough that the move would affect very >> little code; I'm seeking validation of this. If nobody speaks up about >> it, moving intern() would be okay with me. > > You don't want to get rid of 'interning' (e.g. PyString_Intern*()) > but just the intern() built-in? We actually use both, but we use the > C API call much more frequently than the built-in call. I don't > think it would be too painful for us if intern() was removed, but > OTOH if it was stuck in some Python internals module (sys?) and not > kept as a built-in, that would be fine too. Yes, exactly that is proposed: sys.intern() instead of intern(). Georg
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-3000 mailing list