Might I be so bold as to recommend not using print in the first place? Print's behavior changes depending on the environment, the capabilities of your terminal, and if you're piping to something else.

Instead teach people how to use sys.stdout to get properly deterministic behavior.

Print is useful in the repl, and in quick one-offs, but I would never use it for production deployments. And I never let it survive a code review either. It's bad practice to rely on it.

It's better in Python3, but I'd still probably use explicit file streams.