Benjamin Peterson benja...@python.org added the comment:
Fixed in r73981.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2412
___
Changes by Daniel Diniz aja...@gmail.com:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2412
___
___
Python-bugs-list
David Wolever [EMAIL PROTECTED] added the comment:
Here is a patch that will detect a `from __future__ import print_function`
and adjust the grammar appropriately.
Any objections?
--
keywords: +patch
Added file: http://bugs.python.org/file10081/print_function_detection.diff
Changes by David Wolever [EMAIL PROTECTED]:
--
assignee: collinwinter - David Wolever
nosy: +David Wolever
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2412
__
___
David Wolever [EMAIL PROTECTED] added the comment:
I've updated the fixer (checkin to come shortly), but 2to3 gets upset when
you it comes across print statements with kwargs (eg: print(spam, end=
)), so the tests will be commented out 'till this is fixed.
__
David Wolever [EMAIL PROTECTED] added the comment:
As of r61635, the fix_print fixer has been fixed and tests have been added
(which will ``assert False`` when 2to3 is fixed so it can handle
``print(**kwargs)``).
--
assignee: David Wolever - collinwinter
New submission from Eric Smith [EMAIL PROTECTED]:
Issue 1633807 is a backport of the print function to 2.6, using a
__future__ import. Once it is committed, we need to ensure that 2to3
does the right thing (namely, nothing) with print functions in modules
that have the __future__ import.
