"This is partially in response to Chris', Why Python 3k Shouldn’t Be Ruby (and a mention of Erlang) and my investigation on what I see Python 3000 as being, in plain English..."

"I'm glad to see the first beta of the so-called Python 3000. But for a version that's supposed to break all the rules to become better, I'm not seeing what I think is most important."

Python 3000 (a.k.a. "Py3k", and released as Python 3.0) is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed.

The Ministry of Education from Brazil is buying more 3000 Debian GNU / Linux computers , with four multimedia terminals and compatible printers for installing at 3000 rural schools, with 36 months contractual support. This next bidding adds up to the previous 90000 Debian GNU / Linux computers, network and printers.

Python is a great programming language and one of the easiest to learn. That doesn't mean that it isn't capable of powerful stuff, however, because Python is known to handle almost every kind of programming task quite well. From basic scripting to enhanced graphical 3D programs: Python can do it all.

Just one week shy of Christmas 2008, the Python world saw the release of version 3 of Python. Big deal, eh? Well ... it turns out it was and is, as Python 3 is the first major release of Python designed from the get-go to be incompatible with prior versions of the language.

"In September of last year, I was contracted by an independent investor to do the server side implementation of a Web 2.0 application from the ground up. It was an exciting new project, one which kept me up late at night through many nights, doing design and development. It had been a very long time since I had worked on a project that I found so exciting that it replaced my need for sleep.

Python 2.7, the last in the legacy Python 2.x dynamic language line, moved closer to general availability earlier this month when developers of the language put out a release candidate.

Once again, we do apologize for the long wait and size of this update, but many hiccups along the way conspired against us. The Rippers have been working for months on this to make it as trouble free as humanly possible. We're hoping there won't be too many problems.