http://bugs.python.org/issue3618 is a release blocker due to deadlock in the io library.
and the related C RLock implementation in http://bugs.python.org/issue3001 at this point in the release process. Its obviously missed beta3 which is why I suggested in 3001 that it was too late. That was before I knew about 3618. IMHO for py3k there is a compelling reason to go ahead with it the C RLock implementation for use with io. thoughts? -gps PS I'd also love to see a fast RLock in 2.6 but realize the cutoff has already passed.. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
