News for hackers. Stuff that matters.
Re:Python 3000 is ready by jodrellblank on Wednesday December 03, 2008 @07:05PM (#385051)
I can't believe it's not vaporware.

I can't believe they've ruined years of boasting about how hello world is as simple as "print 'hello world'" by making print a function. :(

Re:Python 3000 is ready by jmtulloss on Wednesday December 03, 2008 @10:09PM (#385243)
Is print("Hello World") really any different than print "Hello World"? The first seems more clear.
Re:Python 3000 is ready by riobard on Wednesday December 03, 2008 @11:02PM (#385282)
I think print("hello world") is better because it is more consistent (mentally)
Re:Python 3000 is ready by jamesbritt on Wednesday December 03, 2008 @11:23PM (#385297)
Doesn't Python make a distinction between some_method and some_method(), where the first is a direct reference to a Method object (more or less) and the second actually invokes that method?
Re:Python 3000 is ready by jmtulloss on Thursday December 04, 2008 @01:38AM (#385396)
Yes, all functions are objects. The thing is, "print" used to be a part of the language, not a function, so you couldn't treat it like a function.
Re:Python 3000 is ready by jodrellblank on Thursday December 04, 2008 @07:59AM (#385613)
Previously: 5 keypresses, Now: 9 keypresses

Previously: 2 characters that aren't directly relevant to what you want to do (print text, the quotes), Now: 4 (quotes and parens).

Previously: No shifted characters, Now: 2 shifted characters

Previously: Inconsistent behaviour, right in the core of the language where you are most likely to benefit from minor savings and least likely to forget about it. Now: Consistent behaviour at the expense of extra typing, visual clutter and, for experienced users, the hassle of changing.

Previously: Python loved for its interactive interpreter, only really possible because Python is concise enough to use in a throw-away fashion.

Yes it's different, the question is, is it an improvement, and is it significant enough to be worth it?

The question is, given all the changes to unicode and classes and iterators and final removing of the int/long split which are all going to play out over big programs and many days/months, why not pick on the color of the bike shed 'issue', extrapolate it over the whole of Py3k and make out of proportion complaints?

Er, wait...

Re:Python 3000 is ready by tocomment on Wednesday December 03, 2008 @08:28PM (#385130)
I had the same thought. I'm torn on that.
Re:Python 3000 is ready by mojuba on Thursday December 04, 2008 @05:43AM (#385538)
If it was only that.

How about "Unicode, only Unicode, nothing but Unicode"? Doesn't it smell Microsoftish/Sunish? 16-bit data is a pain in the arse, and as long as communication hardware is essentially 8-bit, Unicode will never replace old good 8-bit and UTF. It will only make your I/O programming harder and the programs themselves slower, with no real benefit. UTF-8 gives you a perfect solution for all your localization needs without any special support on the compiler side.

I have mixed feelings about Python "3000". Many changes are meant to bring more consistency (if saying you shouldn't do this because it's bad is called "consistency"), however, as a result Python 3 will successfully make it into the corporate environments, but will never be truly popular among geeks. Stick with 2.6, it's nice.

Re:Python 3000 is ready by EliAndrewC on Thursday December 04, 2008 @09:56AM (#385706)
They introduced a new "bytes" type which is basically just the old "str" type. So you can still do things the old way; if you say b"Hello World!" then it'll give you the bytes type, whereas if you say "Hello World!" then it'll give you the unicode str type.