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 Robin.Schreiber
Recipients Robin.Schreiber, asvetlov, loewis, ned.deily
Date 2012-10-06.17:04:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349543049.33.0.965980508236.issue15721@psf.upfronthosting.co.za>
In-reply-to
Content
Before I submitted this patch, I used to have these variables inside the modulestate, which caused severe problems. I do not know the exact reason, but my guess is that these variables have to be globally available for every thread (tcl variables are used for thread synchronization arent they?). As the modulestate may change depending on the thread, one can no longer guarantee that every thread within the process is operating on the same variable. This might not be nessecary, however as I mentioned, the naive approach of putting the variables inside the modulestate did not work out for me.
History
Date User Action Args
2012-10-06 17:04:09Robin.Schreibersetrecipients: + Robin.Schreiber, loewis, ned.deily, asvetlov
2012-10-06 17:04:09Robin.Schreibersetmessageid: <1349543049.33.0.965980508236.issue15721@psf.upfronthosting.co.za>
2012-10-06 17:04:09Robin.Schreiberlinkissue15721 messages
2012-10-06 17:04:08Robin.Schreibercreate