[issue15097] Improving wording on the thread-safeness of import

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue15097] Improving wording on the thread-safeness of import

Irit Katriel added the comment: The threading doc no longer mentions import at all. Any objections to closing this issue as out of date? Or is there anything else to look into here? -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___

[issue15097] Improving wording on the thread-safeness of import

Merlijn van Deen added the comment: First off, thank you for your response. > The existence of an import lock is deliberately omitted from the text, > and the reader is supposed to abide by the restriction as written > regardless of the motivation behind it. > The entire notion of an import lo

[issue15097] Improving wording on the thread-safeness of import

Martin v. Löwis added the comment: > which, I think, fails to make the main point: I disagree. It currently makes it main point, but stops doing so under your rephrasing. The main point of that section is "While the import machinery is thread-safe, there are two key restrictions on threaded im

[issue15097] Improving wording on the thread-safeness of import

Changes by Merlijn van Deen : Added file: http://bugs.python.org/file26038/deadlock.py ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue15097] Improving wording on the thread-safeness of import

Changes by Merlijn van Deen : Removed file: http://bugs.python.org/file26037/deadlock.py ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15097] Improving wording on the thread-safeness of import

New submission from Merlijn van Deen : http://docs.python.org/library/threading.html#importing-in-threaded-code Currently, the documentation states "Firstly, other than in the main module, an import should not have the side effect of spawning a new thread and then waiting for that thread in any