4 ms·
The community will fork the 2.7 codebase and continue to support it, even if Python.org EOLs it.
by loeg 10y ago
The community will fork the 2.7 codebase and continue to support it, even if Python.org EOLs it.
- xrange 10y agoIt looks like all Python 2.8 is missing is a new name: https://www.naftaliharris.com/blog/why-making-python-2.8/ https://www.naftaliharris.com/blog/why-making-python-2.8/
- ensignavenger 10y agoI can see "the community" doing security fixes, maybe some bug fixing and a few back ports, but so far I havn't seen much effort from any community to bring active development of new features.
- loeg 10y agoIt seems like the 2.7 community is happy enough without the new features -- just need the bugfixes and continued backwards compatibility to keep that segment happy. From a new features perspective, the other reply's Placeholder is fascinating. (I haven't looked into it thoroughly yet.)
- ensignavenger 10y agoIt is certainly interesting if it truly materializes. But it looks like the plan is to mostly backport stuff from py3- so py3 is still the future, with Placeholder getting some of those features eventually. And that is great from a legacy codebase perspective.
- loeg 10y agoRight.