Nick Coghlan added the comment: I think a) is worth doing regardless - in many cases, third party libraries will be dealing with function, generator or coroutine objects, rather than with code objects directly, so they'll benefit even if the updated API remains private to the interpreter.
So let's narrow the scope of this particular issue to just that, and defer the idea of a new public API for the time being. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2786> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
