This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
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

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.
Date User Action Args
2016-09-09 23:34:07vstinnersetrecipients: + vstinner, gvanrossum, doko, ned.deily, xdegaye, python-dev, zach.ware, koobs
2016-09-09 23:34:07vstinnersetmessageid: <>
2016-09-09 23:34:07vstinnerlinkissue28027 messages
2016-09-09 23:34:07vstinnercreate