This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ethan.furman
Recipients Maciej Gol, brett.cannon, eric.snow, ethan.furman, lars.gustaebel, ncoghlan, serhiy.storchaka
Date 2020-01-24.18:06:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579889170.2.0.104923361304.issue39430@roundup.psfhosted.org>
In-reply-to
Content
Brett:
------
> It's covered in the language reference where import semantics are
> explained. It isn't explicitly called out in higher-level docs that
> I'm aware of because it only really comes up in edge cases like
> importing in a thread which we actively discourage unless there's a
> compelling reason not to.

When was this change made?  Assuming it is, in fact, a change.  It seems like most of the stdlib could be called in a thread, so the practice of lazily importing a module wholesale might need to be audited and proactively fixed.  Maybe that could be a newcomer's easy(ish) project?
History
Date User Action Args
2020-01-24 18:06:10ethan.furmansetrecipients: + ethan.furman, brett.cannon, ncoghlan, lars.gustaebel, eric.snow, serhiy.storchaka, Maciej Gol
2020-01-24 18:06:10ethan.furmansetmessageid: <1579889170.2.0.104923361304.issue39430@roundup.psfhosted.org>
2020-01-24 18:06:10ethan.furmanlinkissue39430 messages
2020-01-24 18:06:10ethan.furmancreate