This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients rhettinger, ronaldoussoren, rushter
Date 2018-08-13.08:23:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534148624.65.0.56676864532.issue34386@psf.upfronthosting.co.za>
In-reply-to
Content
IMHO we shouldn't expose the intern dictionary without there being a clear, and good enough, use case for doing so.  

Exposing the dictionary decreases implementation flexibility, and increases requirements on other implementations.  One example of the former: at least in theory the interning dictionary could be a set, but we couldn't make that change if the dictionary were exposed in the API.

With current information I'm -1 on exposing the dictionary, and -0 on doing that for debug builds only.
History
Date User Action Args
2018-08-13 08:23:44ronaldoussorensetrecipients: + ronaldoussoren, rhettinger, rushter
2018-08-13 08:23:44ronaldoussorensetmessageid: <1534148624.65.0.56676864532.issue34386@psf.upfronthosting.co.za>
2018-08-13 08:23:44ronaldoussorenlinkissue34386 messages
2018-08-13 08:23:44ronaldoussorencreate