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 ale2017
Recipients ale2017, ezio.melotti, serhiy.storchaka
Date 2017-04-15.08:21:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643e354-bf50-dff0-85c5-930d864fc16d@tana.it>
In-reply-to <1492236741.36.0.0135431478162.issue30011@psf.upfronthosting.co.za>
Content
Serhiy's analysis is correct.  If anything more than a comment is going
to make its way to the code, I'd suggest to move dictionary building to
its own function, so that it can be called either on first use --like
now-- or before threading if the user is concerned.

I agree there is nothing wrong with multiple builds.  My point is just a
minor, bearable inefficiency.  It can be neglected.  Its most annoying
case is probably with test suites, which are more likely to shoot up a
bunch of new threads all at once.

Greetings
Ale
History
Date User Action Args
2017-04-15 08:21:05ale2017setrecipients: + ale2017, ezio.melotti, serhiy.storchaka
2017-04-15 08:21:05ale2017linkissue30011 messages
2017-04-15 08:21:05ale2017create