Barry Warsaw writes: > I would like to make a definitive statement as to 2.7's EOL because > I think that will spur more people to work on porting.
I have to agree with the people who say that it's not a major spur. Internal support for existing Python 2.7 installations is by now quite a bit less than a full-time job (at least the part corresponding to what python-dev does for a version in late maintenance releases[1]). I don't see how it makes the choice between sticking with 2.7 vs. contributing ports to 3.x more stark than it already is. Of course it does free up core developer time, especially the release engineers. In maintaining 2.7 past 2015, are core developers really doing anything that a business can't do cheaply and with maximum social benefit?[2] Footnotes: [1] Maybe the Windows build process brings it close to that order of magnitude, if users are building internally. But this should be a saleable product. [2] It has been proved that open source development styles *do* provide benefits *beyond* what business can profitably provide, because of network externalities among developers and users, especially the ability of user-developers to contribute. But these benefits mostly disappear when the developer-vs-user externality disappears because the spec is fixed, and the implementation 99.44% corresponds to the spec. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
