[Python-Dev] Python 2.7 patch levels turning two digit (original) (raw)
Ethan Furman ethan at stoneleaf.us
Mon Jun 23 23:19:13 CEST 2014
- Previous message: [Python-Dev] Python 2.7 patch levels turning two digit
- Next message: [Python-Dev] Python 2.7 patch levels turning two digit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 06/21/2014 02:48 PM, Ethan Furman wrote:
On 06/21/2014 02:37 PM, M.-A. Lemburg wrote:
My answers to these are: 1. We should use dynamic linking instead and not let OpenSSL bugs trigger Python releases; 2. It's not a big problem; 3. Yes, please, since it is difficult for people to develop and debug their extensions with a 2008 compiler, when the rest of the world has long moved on. +1 (assuming not incredibly difficult and those that can are willing ;)
Revising this to:
+1, -0, -1
It seems to me the intention of supporting 2.7 for so long was not to give ourselves additional nightmares, but to provide a basic level of support for those who are needing longer time before migrating. One of the reasons to migrate is to avoid future pain (pain is an excellent motivator -- it's why we don't go to the doctor when we're healthy, right? ;) If getting new or updated modules becomes more painful then that's motivation to upgrade -- not motivation for us to make both our lives (with the extra work) and everyone's else lives (why isn't this module working? oh, wrong compiler) more difficult.
--
Ethan
- Previous message: [Python-Dev] Python 2.7 patch levels turning two digit
- Next message: [Python-Dev] Python 2.7 patch levels turning two digit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]