Skip to content
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.

Sign up for GitHub

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

Jump to bottom

nbconvert incompatible with Windows? #3534

Closed
jakevdp opened this issue Jul 4, 2013 · 1 comment · Fixed by #3539
Closed

nbconvert incompatible with Windows? #3534

jakevdp opened this issue Jul 4, 2013 · 1 comment · Fixed by #3539
Milestone
1.0

Comments

@jakevdp
Copy link
Contributor

jakevdp commented Jul 4, 2013

This is just speculation, but the way pathnames are defined in IPython/nbconvert/exporters/exporter.py looks like it will cause problems on windows systems. os.path.join should be used in favor of hard-coded paths.

I don't have a windows machine to test this out on, though.
@minrk
Copy link
Member

minrk commented Jul 4, 2013

that may well be - most things start out broken on Windows around here, then get fixed up at a later stage.

minrk added a commit to minrk/ipython that referenced this issue Jul 4, 2013
@minrk
Don't hardcode posix paths in nbconvert
d8cbebe 
use `os.path` for building paths

closes ipython#3534
This was referenced Jul 4, 2013
Merged
Closed
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
@minrk
Don't hardcode posix paths in nbconvert
e31da96 
use `os.path` for building paths

closes ipython#3534
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0
Development

Successfully merging a pull request may close this issue.

Don't hardcode posix paths in nbconvert minrk/ipython
2 participants
@minrk @jakevdp