Martin v. Löwis wrote: >> I'm not sure, but isn't that thread-unsafe? > > You are right; it's thread-unsafe. > > I would fix it by catching the RuntimeError, and retrying. Given the > current GIL strategy (including proposed changes to it), it won't happen > two times in a row, so the number of retries would be bounded.
It's also one of the major reasons for not sharing mutable containers between threads if you can avoid it (and serialising access to them if you can't) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
