Brett Cannon <br...@python.org> added the comment: So David's right that local commits are bad from a threading perspective. If you happen to have an import trigger a thread which itself triggers an import you will lock up the interpreter. Typically this is avoided by not importing anything in a thread and not launching a thread based on an import. But some people do and they eventually get bit by calling a function that they didn't realize would trigger an import as a side-effect.
Since the code duplication has been solved in Python 3 I say add a comment about the duplication and be done with it for ease of development and complete backwards-compatibility. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8143> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
