Martin v. Löwis wrote:
> I'd like to remove support for Windows 9x (95, 98(SE), ME)
> soon from the Python trunk. This would primarily affect all
> wide-string APIs (which would be considered present
> unconditionally), as well as certain "new" Win32 functions;
> in this cleanup, I would also drop
I'd like to remove support for Windows 9x (95, 98(SE), ME)
soon from the Python trunk. This would primarily affect all
wide-string APIs (which would be considered present
unconditionally), as well as certain "new" Win32 functions;
in this cleanup, I would also drop support for NT+ before
Windows 20
Zitat von Trent Mick <[EMAIL PROTECTED]>:
> 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 als
[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 q
2006/2/24, Neal Norwitz <[EMAIL PROTECTED]>:
> 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
[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
On 2/24/06, Michael Foord <[EMAIL PROTECTED]> wrote:
> 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
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 W
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 Pyth
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.
>>
>
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
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
12 matches
Mail list logo
