Ross Cohen <rco...@snurgle.org> added the comment: On Fri, 29 Jan 2010 21:15:14 +0000 Marc-Andre Lemburg <rep...@bugs.python.org> wrote:
> Breaking existing applications and ports of Python for 2.7 > certainly won't make anything easier for anyone. > > For 2.7 we will certainly not allow the above to happen, > since that's the version that's going to be used by most > people for a few years to come. > > What we could do for 2.7, is add Py3k deprecation warnings > to the alternative thread implementations, mentioning their > removal in 3.2. What if, as you proposed earlier, the patch were to leave the old behavior if the threading model on the given platform were not supported? Ross ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7753> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
