-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nbconvert fails with unicode preprocessor names #362
Comments
Won't adding an |
I don't think adding an 'r' is a solution. I get similar errors when I remove the prepocessor part, too. Any ideas what to look for ? |
JSON is conceptually unicode, and I think the JSON module leans towards returning parsed JSON strings as unicode. I guess you're probably just the first person to run into this: importable names listed in a JSON config file, parsed by Python 2. |
Thanks so much, @juhasch ! I had the exact same problems with nbconvert after installing the same nbextensions collection you mention, and after copying and pasting your edits all is good. (Probably not the correct way to use github, but it worked!) |
Am I correct in saying that #370 addresses this? |
Not sure if @michaelpacer 's question was directed at me, but to be specific, after making the changes described in the following two commits, the problem was fixed/ |
Thanks a lot, this fix was enough for me: |
I get the following error with
nbconvert
after installing custom preprocessors available injupyter_contrib_nbextensions
from conda-forge into a Python 2.7 environment:It looks like this is a unicode problem with Python 2.7. This is the default
jupyter_nbconvert_config.json
file:Adding
r
to the preprocessor strings makes it work again:Nbconvert version is 4.2.0 on Linux Mint.
The text was updated successfully, but these errors were encountered: