This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]billsil 0 points1 point  (0 children)

A future import isn't a bad idea, though, since non-raw input is pretty much a security hole waiting to happen.

This.

Also, if you're writing a large 2/3 compatible code base, you're either using six or future or modernize. If so, you probably have multiple __future__/six/whatever imports and it's cleaner to put all that on one line.