3 ms·
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 prin
by jodrellblank 18y ago
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. :(
- tocomment 18y agoI had the same thought. I'm torn on that.
- jmtulloss 18y agoIs print("Hello World") really any different than print "Hello World"? The first seems more clear.
- riobard 18y agoI think print("hello world") is better because it is more consistent (mentally)
- jamesbritt 18y agoDoesn'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?
- jmtulloss 18y agoYes, 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.
- benn 18y agolol i cant believe you numskulls didnt get his joke. unless the OP was a tard too? :/
- jodrellblank 18y agoPreviously: 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...
- deleted 18y ago[deleted]
- mojuba 18y agoIf 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.
- EliAndrewC 18y agoThey 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.