Comment 3 for bug 300874

You can Use The Source James :) __future__ is a regular python package, I don't have a python3k handy but I'm pretty sure the package is still there. After all it exists to ensure forward compatibility, it will be a bit strange that it can break backward compatibility.

By the way, what is the rationale with checking imports from __future__ ? Do you have examples where it break things ?