Stefan Behnel <sco...@users.sourceforge.net> added the comment: The problem with having that information "internally" is that it's currently stored in local variables in the call chain from the dynamic library loader. Passing that information on into a callable function, without passing it as an argument into the init function, means, that it needs to get stored away in some global place, with all the drawbacks that this induces. That's what Martin was referring to.
I agree with Martin that the idea of adding a parameter to the module init function is not worth pursuing before Python 4, so I'm closing this bug. ---------- resolution: -> postponed status: open -> closed title: Pass context information into the extension module init function -> Pass context information into the extension module init function _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13431> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
