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 bkline
Recipients bkline, dmalcolm, eli.bendersky, flox, kaifeng, neologix, pitrou, python-dev, tim.peters, vstinner
Date 2018-01-16.09:43:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for your responses to my comments. I'm working as hard as I can to get my customer's systems migrated into the Python 3 world, and I appreciate the efforts of the community to provide incentives (such as the resolution for this failure) for developers to upgrade. However, it's a delicate balancing act sometimes, given that we have critical places in our system for which the same code runs more than twice as slowly on Python 3.6 as on Python 2.7.
Date User Action Args
2018-01-16 09:43:00bklinesetrecipients: + bkline, tim.peters, pitrou, vstinner, eli.bendersky, flox, dmalcolm, neologix, python-dev, kaifeng
2018-01-16 09:43:00bklinesetmessageid: <>
2018-01-16 09:43:00bklinelinkissue11849 messages
2018-01-16 09:43:00bklinecreate