python - Why does using from future import print_function breaks Python2-style print?

Question

I am new at programming with python, and I am trying to print out with a separator and end but it is still giving me a syntax error.

I am using python 2.7.

Here is my code:

from __future__ import print_function
import sys, os, time

for x in range(0,10):
    print x, sep=' ', end=''
    time.sleep(1)

And here is the error:

$ python2 xy.py
  File "xy.py", line 5
    print x, sep=' ', end=''
          ^
SyntaxError: invalid syntax
$

You imported print as a function but you're still treating it as a statement. — jonrsharpe
you can't call print without the parenthesis because you have changed print to be a function print(args) — Charlie Parker
See also What is __future__ in Python used for and how/when to use it, and how it works — Helen
You are still using python 2 print syntax, but you imported the print function from the future (aka the print function inside python 3). It replaces the old print syntax with the new syntax, thus creating an error — CrazyVideoGamer
Also, I don't know why you are still using python 2, when python 3 is out, but whatever. — CrazyVideoGamer

Cyphase Cyphase · Accepted Answer · 2015-08-16T07:11:59

First of all, from __future__ import print_function needs to be the first line of code in your script (aside from some exceptions mentioned below). Second of all, as other answers have said, you have to use print as a function now. That's the whole point of from __future__ import print_function; to bring the print function from Python 3 into Python 2.6+.

from __future__ import print_function

import sys, os, time

for x in range(0,10):
    print(x, sep=' ', end='')  # No need for sep here, but okay :)
    time.sleep(1)

__future__ statements need to be near the top of the file because they change fundamental things about the language, and so the compiler needs to know about them from the beginning. From the documentation:

A future statement is recognized and treated specially at compile time: Changes to the semantics of core constructs are often implemented by generating different code. It may even be the case that a new feature introduces new incompatible syntax (such as a new reserved word), in which case the compiler may need to parse the module differently. Such decisions cannot be pushed off until runtime.

The documentation also mentions that the only things that can precede a __future__ statement are the module docstring, comments, blank lines, and other future statements.

python - Why does using from __future__ import print_function breaks Python2-style print?

1 Answers

python - Why does using from future import print_function breaks Python2-style print?