Message98542
| Author |
rcohen |
| Recipients |
brian.curtin, jnoller, kevinwatters, lemburg, nascheme, pitrou, rcohen, schmir |
| Date |
2010年01月29日.22:33:30 |
| SpamBayes Score |
1.2519386e-07 |
| Marked as misclassified |
No |
| Message-id |
<20100129143020.67f0ff65@neeble> |
| In-reply-to |
<4B634FDD.50700@egenix.com> |
| Content |
On 2010年1月29日 21:15:14 +0000
Marc-Andre Lemburg <report@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 |
|