Live data from Hacker News

Python 3.0 Released

python.org

1–10 of 63 posts

Re: Python 3.0 Released

#3
So much cleaner and more consistent. Classic classes are gone for good!

Unlike with other languages (which I won't name for fear of offense!) I think Pythonistas will actually migrate to this much improved Python (well, forgetting the 10% performance hit) especially as such focus has been put into making tools to make it easier, unlike with PHP 4->5 (oops..!)

Re: Python 3.0 Released

#5
Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for.

It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline.

For now I'm sticking with python 2.5 - since it's the best one considering it's far better module, and platform support.

Re: Python 3.0 Released

#6
post #5

Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for. It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline. For now I'm sticking with python 2.5 - since it's the best one considering it's far bette…

> Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for.

From the release page (http://www.python.org/download/releases/3.0/): This is a production release; we currently support these formats: ...

That said, I also plan to keep my core projects on 2.x for a few more months till django, ipython, debian repos etc. move to 3.x. But I do plan to play with 3.x some.

Re: Python 3.0 Released

#7
post #5

Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for. It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline. For now I'm sticking with python 2.5 - since it's the best one considering it's far bette…

> It's going to take ages for modules to get converted over...

You underestimate the power of the ... wait a sec. :)

Anyway, there's broad support and excitement in the community about this release. I think you'll see modules being updated more quickly than you suspect.

Re: Python 3.0 Released

#8

So much cleaner and more consistent. Classic classes are gone for good! Unlike with other languages (which I won't name for fear of offense!) I think Pythonistas will actually migrate to this much improved Python (well, forgetting the 10% performance hit) especially as such focus has been put into making tools to make it easier, unlike with PHP 4->5 (oops..!)

I'll miss __coerce__. :(

Re: Python 3.0 Released

#10
post #5

Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for. It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline. For now I'm sticking with python 2.5 - since it's the best one considering it's far bette…

I think that's python2.6
Post reply on HN