4 ms·
Is print("Hello World") really any different than print "Hello World"? The first seems more clear.
by jmtulloss 18y ago
Is 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]