nbconvert to pdf fails after updating OS X to El Capitan #8935

Closed
Oxtay opened this Issue Oct 28, 2015 · 7 comments

Comments

Projects
None yet
4 participants
@Oxtay

Oxtay commented Oct 28, 2015

Yesterday I converted one of my notebooks to PDF. This morning I upgraded my OS X to the new El Capitan and trying the same conversion today, I got this message:

nbconvert failed: command could not be found: pdflatex

I tried a few different things, including updating ipython from 3.1.x to 4.0.0, installing mistune through pip (because somewhere midway it started complaining about that), and updating homebrew. It seems only the message has changed slightly, but I assume it basically means the same thing:

nbconvert failed: pdflatex not found on PATH

Not sure if this is an error related to El Capitan or ipython.

@crocha700

This comment has been minimized.

Show comment
Hide comment
@crocha700

crocha700 Oct 29, 2015

Could you just do $ which pdflatex and tell me what you get?

Could you just do $ which pdflatex and tell me what you get?

@Oxtay

This comment has been minimized.

Show comment
Hide comment
@Oxtay

Oxtay Oct 29, 2015

It actually returns nothings. It seems that it might be related to issue described here about El Capitan.

On a different note, I may have to create another issue for this or it may have been solved, but I noticed that calling ipython notebook with --profile and --color no longer works. Would you happen to know if there is a solution?

Edit: I just fixed the paths and added the pdflatex path to bashrc. now for which pdflatex I get /Library/TeX/texbin/pdflatex but I still get that pdflatex not found on PATH.

Oxtay commented Oct 29, 2015

It actually returns nothings. It seems that it might be related to issue described here about El Capitan.

On a different note, I may have to create another issue for this or it may have been solved, but I noticed that calling ipython notebook with --profile and --color no longer works. Would you happen to know if there is a solution?

Edit: I just fixed the paths and added the pdflatex path to bashrc. now for which pdflatex I get /Library/TeX/texbin/pdflatex but I still get that pdflatex not found on PATH.

@shaun10

This comment has been minimized.

Show comment
Hide comment
@shaun10

shaun10 Dec 1, 2015

Oxtay, know issue has been unresolved for a month but did you try installing python via brew? then installing jupyter/ipython? From there I would try to install pdflatex and echo, which the path back to us for you python install.

shaun10 commented Dec 1, 2015

Oxtay, know issue has been unresolved for a month but did you try installing python via brew? then installing jupyter/ipython? From there I would try to install pdflatex and echo, which the path back to us for you python install.

@shaun10

This comment has been minimized.

Show comment
Hide comment
@shaun10

shaun10 Dec 1, 2015

Also looks like Latex and MacTex require symbolic link updates once the download is finished unfortunately.

shaun10 commented Dec 1, 2015

Also looks like Latex and MacTex require symbolic link updates once the download is finished unfortunately.

@takluyver takluyver added this to the not ipython milestone Jan 26, 2016

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Jan 26, 2016

Member

Are you doing the conversion from the notebook interface? How are you starting the notebook. If you start it from a GUI mechanism in OS X, it won't pick up your changes to $PATH in .bashrc.

Member

takluyver commented Jan 26, 2016

Are you doing the conversion from the notebook interface? How are you starting the notebook. If you start it from a GUI mechanism in OS X, it won't pick up your changes to $PATH in .bashrc.

@takluyver takluyver modified the milestones: no action, not ipython Jan 26, 2016

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Jan 26, 2016

Member

Closing as probably not a bug, feel free to continue discussing.

Member

takluyver commented Jan 26, 2016

Closing as probably not a bug, feel free to continue discussing.

@takluyver takluyver closed this Jan 26, 2016

@Oxtay

This comment has been minimized.

Show comment
Hide comment
@Oxtay

Oxtay Jan 26, 2016

I can no longer recreate the issue.
Thanks.

Oxtay commented Jan 26, 2016

I can no longer recreate the issue.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment