2to3 converts raw_input() calls into input(), and input() runs all user data through eval(). This opens a hole in previously secure Python2.x applications.

Is the author of this change aware of the issue?

`input()` in Python 3 is the same as `raw_input()` in Python 2. It does not evaluate the input as Python code.

This is incorrect. Please look at Python/bltinmodule.c for how input() is implemented - there is no eval involved.

Sorry. I've incidentally run converted file with Python 2.x.

To avoid future confusions, should there be a reference in 2to3 docs to the behavior change for input() function?

From http://docs.python.org/library/2to3#2to3fixer-raw_input to http://docs.python.org/py3k/whatsnew/3.0.html#builtins

I find http://docs.python.org/dev/library/functions#input clear enough.  Remember that 3.x is a clean cut, it does not carry information for 2.x users; those have enough information with http://docs.python.org/py3k/whatsnew/3.0#builtins IMO.