Why Turn "Print" into "Print()"????

[Sverker Nilsson]

I had bothered. Volunterly that is too. Becausa I care.

Should we piss of about py3k? It's a debate.

Guiod wrote also something he got from Ruby: "Open source need to
change or die"

If I recall correctly. I cant get too bothered for I get tired too.

But change is not == progress.

Sometimes it is like in the 70s here when we had even worse economy
"Well, at least it gives some work opportunities"

Think about it. It is Less work that is the ideal, the thing to strive
for
Not More work - it may look to give more money but it is really not
economic

So is it this the way ? No ? It ain't broken so lets brake it

S


On May 27, 10:15 am, alex23 <wuwe... at gmail.com> wrote:
> On May 27, 5:47 pm, Sverker Nilsson <s... at sncs.se> wrote:
>
> > Dont make they functions. Or is this just to throw us out?
>
> Have you even bothered to read the reasoning for this change since the
> last time you got your knickers twisted over it?
>
> http://www.python.org/dev/peps/pep-3105/#rationale
>
> I don't see "piss everyone off" listed there anywhere.
>
> Personally, I believe if you're writing code of any serious length,
> you generally shouldn't be using 'print' anyway, using the logging
> module allows for a lot more flexibility.
>
> If you're bothered by having to type the parentheses while in the
> interpreter, try using IPython with it's autocall mode turned on.