Ronald Oussoren <ronaldousso...@mac.com> added the comment:
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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34386> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
