Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this. The Python 2.5 installer will present a warning message on the systems which will not be supported in Python 2.6. n
Neal Norwitz wrote:
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this.
The Python 2.5 installer will present a warning message on the systems which will not be supported in Python 2.6.
Hey, someone even wanted to continue supporting DOS... Georg
Georg Brandl wrote:
Neal Norwitz wrote:
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this.
The Python 2.5 installer will present a warning message on the systems which will not be supported in Python 2.6.
Hey, someone even wanted to continue supporting DOS...
A lot of people are still using Windows 98. But I guess if noone is volunteering to maintain the code... Michael Foord
Georg
_______________________________________________ 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/fuzzyman%40voidspace.org.u...
On Fri, Feb 24, 2006, Michael Foord wrote:
Georg Brandl wrote:
Neal Norwitz wrote:
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this.
The Python 2.5 installer will present a warning message on the systems which will not be supported in Python 2.6.
Hey, someone even wanted to continue supporting DOS...
A lot of people are still using Windows 98. But I guess if noone is volunteering to maintain the code...
DOS has some actual utility for low-grade devices and is overall a simpler platform to deliver code for. At the standard 18-month release cycle, it will be beginning of 2008 for the release of 2.6, which is ten years after Win98. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "19. A language that doesn't affect the way you think about programming, is not worth knowing." --Alan Perlis
On Fri, 24 Feb 2006 10:29:27 -0800, Aahz wrote:
DOS has some actual utility for low-grade devices and is overall a simpler platform to deliver code for. At the standard 18-month release cycle, it will be beginning of 2008 for the release of 2.6, which is ten years after Win98.
The last Windows release of that branch was Windows ME, in September 2000, i.e. you have to wait till 2010 in order to be ten years after the last legacy OS release. Kind regards, Alexander
On 2/24/06, Michael Foord
A lot of people are still using Windows 98. But I guess if noone is volunteering to maintain the code...
Agreed. If they're so keen on using an antiquated OS, perhaps they would be perfectly happy using a matching Python version... Somehow I doubt this is going to be a big deal for anyone affected. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
[Neal Norwitz wrote]
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this.
Are there specific code areas in mind that would be ripped out for this or is this mainly to avoid having to test on and ensure new code is compatible with? Trent -- Trent Mick TrentM@ActiveState.com
2006/2/24, Neal Norwitz
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6.
+1 . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
[Neal Norwitz]
Martin and I were talking about dropping support for older versions of Windows (of the non-NT flavor). We both thought that it was reasonable to stop supporting Win9x (including WinME) in Python 2.6. I updated PEP 11 to reflect this.
It's OK by me, but I have the same question as Trent: [Trent Mick]
Are there specific code areas in mind that would be ripped out for this or is this mainly to avoid having to test on and ensure new code is compatible with?
Seem unlikely it's the latter, since I'm not sure any Python developer tests on a pre-NT Windows anymore anyway. Maybe Raymond is still running WinME? About the former, I don't see much potential. The ugliest 9x-ism is w9xpopen.exe, but comments in the places it's used say it's needed on NT too if the user is running command.com. If so, it stays. There's a bit of excruciating Win9x-specific code in winsound.c that could go away, and I suppose we could assume that Unicode filenames are always supported on Windows. Maybe best is that if someone reports a Win9x-specific bug against 2.6+, we could close it as Won't-Fix at once instead of letting it sit around ignored for years :-)
Zitat von Trent Mick
Are there specific code areas in mind that would be ripped out for this or is this mainly to avoid having to test on and ensure new code is compatible with?
Primarily the non-W versions of the file system API. I think the W9x popen support could also go away. I don't think any testing happens for W9x; I (atleast) can't test it myself (I installed a Windows 95 system to test the 2.4 installer, but had to give up the machine shortly after that). Regards, Martin
participants (10)
-
Aahz -
Alexander Schremmer -
Facundo Batista -
Georg Brandl -
Guido van Rossum -
martin＠v.loewis.de -
Michael Foord -
Neal Norwitz -
Tim Peters -
Trent Mick