I was wondering if anyone has suggestions for writing a backwards-compatible input() call for retrieving a filepath?
In Python 2.x, raw_input worked fine for input like /path/to/file. Using input works fine in this case for 3.x, but complains in 2.x because of the eval behavior.
One solution is to check the version of Python and, based on the version, map either input
or raw_input
to a new function:
if sys.version_info[0] >= 3:
get_input = input
else:
get_input = raw_input
I'm sure there is a better way to do this though. Anyone have any suggestions?
The way you are handling it is just fine. There are probably more similar ways using the
sys
module, but just in keep in mind that if you are program is doing something more than trivial with strings and files, it is better to have two versions of your program instead of having a backwards compatible python3 program.Since the Python 2.x version of
input()
is essentially useless, you can simply overwrite it byraw_input
:In general, I would not try to aim at code that works with both, Python 2.x and 3.x, but rather write your code in a way that it works on 2.x and you get a working 3.x version by using the
2to3
script.My preference is to import the function:
from builtins import input
Although, you will have to install the dependency:
pip install future
Unfortunately this dependency will not be noticed by the
pipreqs
tool. So if you are creatingrequirements.txt
files you'll have to add the future library in manually.This code is taught in many Python education and training programs now.
Usually taught together:
First line: imports the Python 3.x
print()
function into Python 2.7 soprint()
behaves the same under both versions of Python. If this breaks your code due to olderprint "some content"
calls, you can leave this line off.Second and third lines: sets Python 2.7
raw_input()
toinput()
soinput()
can be used under both versions of Python without problems. This can be used all by itself if this is the only compatibility fix you wish to include in your code.There are more
from __future__
imports available on the Python.org site for other language compatibility issues. There is also a library called "six" that can be looked up for compatibility solutions when dealing with other issues.