Message275494
| Author |
vstinner |
| Recipients |
doko, gvanrossum, koobs, ned.deily, python-dev, vstinner, xdegaye, zach.ware |
| Date |
2016年09月09日.23:34:07 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1473464047.82.0.28743517936.issue28027@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Matthias Klose: Maybe you didn't understand something: breaking the backward compatibility was a deliberate choice. It's a matter of maintenance burden versus the number of broken applications.
According to your search, there are only 8 projects in the wild which will break on Python 3.6. Please compare this number to the number of Python modules on PyPI: 88 298 packages, according to https://pypi.python.org/pypi
Moreover, it seems like some of these 8 projects are not compatible with Python 3 yet, so it's not like this specific change broke them...
Finally, I don't like repeating myself, but: fixing these project requires to modify A SINGLE LINE OF CODE. I know well that Debian likes patching packages, it's not like it is something technically impossible.
Please don't reopen the issue again without a very strong argument. |
|