Not sure if this is a bug. We're experiencing it in v3.3.2 and was discovered by accident.

It seems to be possible to define python functions (like print or input) as variables, as if they're not reserved. If you do that, the command functionality is lost until Python is reseted.

For example try this in IDLE:

>>> print = 10
>>> print
10
>>> print(print)
TypeError: int object is not callable
>>> print(10)
TypeError: int object is not callable

Here is a screenshot >

http://imgur.com/IpjELhp

We tested it, and this doesn't happen in v2.

Sorry if this has been reported previously.

Best regards.

Yes, that's the way Python works.  In Python3, print became a function and is no longer a keyword, so yes, it can be shadowed in the local namespace just like any other Python function.

FTR you can always get it back from builtins.print:

>>> print('test')
test
>>> print = 10
>>> print('test')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'int' object is not callable
>>> import builtins
>>> print = builtins.print
>>> print('test')
test

Great, thanks. Didn't know that.

All the best.