encoding issues about nbstripout HOT 9 CLOSED

@geggo Thanks for reporting this! I just did a simple test with a notebook with one code cell with some unicode text in a string and I didn't get any failures. Could you attach the notebook you get the failure with?

from nbstripout.

Thanks for looking at this issue. A simple notebook that shows the problem is: test_unicode.ipynb

from nbstripout.

Nope, sorry, works just fine for me (Python 2.7 on Linux x64). Could this be a Mac or Anaconda issue?

from nbstripout.

@geggo Tried with Anaconda too, no issue either. I'll add your notebook as a regression test, let's see what Travis has to say.

from nbstripout.

Aha, hang on! This is irritating! I do get the error iff I redirect the output to file, not if I just let it go to the terminal. How is that even possible? Redirection should be purely handled by the shell!

from nbstripout.

Your suggested fix works, so I'll pull that in, thanks for this!

from nbstripout.

@geggo: Released in 0.2.3!

from nbstripout.

For the record: redirection can make a difference because code can detect whether the output is a terminal or a pipe (this is how e.g. ls shows files in nice columns when used interactively). In Python's case, its guess of the encoding to use for output is different when output is being piped to a file.

from nbstripout.

@takluyver thanks for highlighting! I did read up on the topic after fixing this but failed to clarify.

from nbstripout.