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 r.david.murray
Recipients brett.cannon, docs@python, eric.snow, ezio.melotti, joshpurvis, ncoghlan, r.david.murray, vstinner
Date 2016-06-27.18:21:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467051699.31.0.490070238931.issue27387@psf.upfronthosting.co.za>
In-reply-to
Content
No, I'm talking about the threading docs, not the encoding docs.  I think that's the only place it matters.  Specifically, in the section that I linked to, in the bullet point that warns against launching threads on import, it can note that even if you try to make your own code avoid the import lock, implicit imports such as the one done by encode/decode can trip you up.
History
Date User Action Args
2016-06-27 18:21:39r.david.murraysetrecipients: + r.david.murray, brett.cannon, ncoghlan, vstinner, ezio.melotti, docs@python, eric.snow, joshpurvis
2016-06-27 18:21:39r.david.murraysetmessageid: <1467051699.31.0.490070238931.issue27387@psf.upfronthosting.co.za>
2016-06-27 18:21:39r.david.murraylinkissue27387 messages
2016-06-27 18:21:39r.david.murraycreate