robert wrote: > > Guess it would be more wise to not expose deepcopy, cPickle.dump etc. to > this kind of RuntimeError unnecessarily. > The speed gain of the iterator-method - if any - is minor, compared to > the app crash problems, which are not easy to discover and work-around > (because they happen rarely on fast computers).
searched the thread, threading module for a function for generally locking/dislocking all other python threads from execution. Did not find something like that. (That would be very useful in some threading applications to protect critical sections without forcing the whole application to be populated with lock objects. Of course, such function should be used with care (and "finally") - but it should be there to make thread programming easier...) Robert -- http://mail.python.org/mailman/listinfo/python-list
