Allow importing when sys.stdout is reassigned on Python 3

[takluyver]

Closes gh-30

sys.stdout.buffer is not guaranteed to exist - e.g. if sys.stdout has been reassigned to an io.StringIO instance, it won't. This is only used by the .interact() method, so it should normally be in interactive cases with 'real' system stdout, but we need at least some fallback for when it isn't - and we certainly need to avoid relying on it at import time.

We should think about the binding order. If sys.stdout is reassigned between importing pexpect and calling the .interact() method, this case (spawn class on Python 3) will pick up the new stdout, but the other cases (spawnu on Python 3, either class on Python 2) won't. However, interact goes on to use direct access to stdout (and stdin) by fileno, so any redirection at the Python level won't be effective anyway.

[jquast]

ahh, yes. Good catch. A little tricky, but approved ;-)

[takluyver]

Thanks. This did actually come up somewhere in tests I was running, though I can't remember where now.

We should start thinking about a 3.1 release some time soon.