Python 2.6 Released
python.org
python.org
Including older versions of win2k, winme, win98 etc. They're not only not supporting it, but they've removed code for older versions of windows.
So if you want to distribute portable apps, don't use 2.6+
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.
-- Ken Thompson
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).
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?
Even .NET is not available on Windows 98/Me: http://www.microsoft.com/downloads/details.aspx?FamilyId=262...
Do you have a reference on Python 2.6 dropping support for win2k?
It is pretty clear that support for WIN2K, at least SP4 is NOT being dropped.
"The support for Windows 95, 98, ME and NT4 has been dropped. Python 2.6 requires at least Windows 2000 SP4."
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?
We're talking at least 1%-3%1 of machines on the internet here. That's a sizable chunk of people.
based on wc3 stats... which aren't all that representative.
# No. This code:
@decorate
def foo(self):
frobnicate()
#is exactly equivalent to:
def foo(self):
frobnicate()
foo = decorate(foo)
http://www.python.org/dev/peps/pep-0318/ @this
@that
@the_other
def foo(self):
frobnicate()
This is what Java people call "aspect oriented programming" and get all excited about, but to us it's no big deal :-)class memoize: def __init__(self, function): self.function = function self.memoized = {}
def __call__(self, *args):
try:
return self.memoized[args]
except KeyError:
self.memoized[args] = self.function(*args)
return self.memoized[args]
@memoize
def fib(n)2.6 supports decorators for other things, including classes.
This is because often 2.6 is slower than 2.5. http://mail.python.org/pipermail/python-dev/2008-September/0...
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)