The fact that MS is keeping Windows 2000 on life support does not mean anyone else should waste their time to support that platform. Running ancient operating systems should come with the expectation of not being able to use new software.
>> But who in his right mind would recommend people to use Windows versions prior to 2000?
I think this is a wrong question in this context. Software developer don't recommend OS to people, he delivers software, and the more platforms he supports, the better.
Moreover, if someone has an old box with 98 or NT, what could he do when he don't want to buy a new PC?
I would, especially for people who use their computers mostly for business. Except for USB and PNP support, Windows 2000 is inferior to NT4SP2.
However the Python guys are probably doing the right thing here because the right approach to making windows based business systems reliable is to disable everything possible on them, isolate them as much as you can, get things working and NOT upgrade them unless you absolutely have to.
Windows XP SP2 is basically the minimum version of Windows that you can use and expect a reasonable user experience. That includes the ability to install new (recently released) software. If you insist on old operating systems, then you should expect to run old applicatoins on them.
Robert Metcalf [the inventor of Ethernet] says that if something comes along to replace Ethernet, it will be called “Ethernet”, so therefore Ethernet will never die. Unix has already undergone several such transformations.
If you make applications for windows, then you would understand that people either can't upgrade or won't. Their old machines don't work with newer versions of the OS's.
For web developers this is fine, since they don't need to install programs. However for those of us that need to install programs, it's going to be sticking with python2.5 (or even 2.3 if you want better compatibility).
That rather depends on your definition of portable - I mean, even if they included win98, you'd still likely be stuck with Python 1.5 for Windows CE 1, and no Python for many systems.
That it works on several of the most common, different, platforms in use today, I vote that counts as "portable" - reasonably so.
Another way of looking at it is not how many Win98 systems are there, but that there is (presumably) nobody willing to jump in and argue and offer to support Python 2.6 on Win98 - so how in demand can it be?
I still don't fully understand decorators, but it's definitely true that implementing context managers with decorators is much more succinct and straightforward than manually writing __enter__ and __exit__ methods. And context managers are definitely a win.
Some things are faster, and some are slower. But for the normal benchmarks mentioned in the release notes (for 2.2, 2.3, 2.4, and 2.5), it's slower overall.
$ python2.6 /opt/local/lib/python2.5/test/pystone.py
Pystone(1.1) time for 50000 passes = 0.867314
This machine benchmarks at 57649.2 pystones/second
$ python2.5 /opt/local/lib/python2.5/test/pystone.py
Pystone(1.1) time for 50000 passes = 0.970622
This machine benchmarks at 51513.4 pystones/second
(which is not to say it's always, or even usually faster; just that it's certainly faster on the standard benchmark)