Skip to content
This repository

Do not accept an ipython_dir that's not writeable #669

Closed
fperez opened this Issue August 03, 2011 · 2 comments

3 participants

Fernando Perez Evan Patterson Min RK
Fernando Perez
Owner

As reported by Eric Jones, a colleague found himself with this problem:

Pylab failed to start after an EPD install, and he was dead in the water.

After poking around, he has a HOMESHARE variable that is set to some strange directory he doesn't know about and also that he does not have write access to. As a result, ipython will not start up. This is a show stopper.

We should add a patch that checks if the get_ipython_dir() is writable. If it isn't, we should use the temp dir or something, or we should not try to write the ipythonrc file, or something. We want to ensure that file permissions don't result in the inabliity to start using the app.

Jason reported progress on the issue:

Ilan and I just looked at it and it appears to be a simple fix. path.py get_home_dir() checks a bunch of environment variables on different platforms looking for a home directory. It checks that the directory exists, but not that it's writable. We can just add check to issue a warning if a given directory isn't writable and move on to the next option.

Min RK minrk referenced this issue from a commit in minrk/ipython August 03, 2011
Min RK check for writable dirs, not just existence, in utils.path
replaces various calls to os.path.isdir and os.path.exists with _writable_dir.

closes gh-669
b1ec990
Min RK
Owner

See PR #670

Min RK minrk referenced this issue from a commit August 03, 2011
Commit has since been removed from the repository and is no longer available.
Min RK minrk referenced this issue from a commit in minrk/ipython August 03, 2011
Min RK use tempdir if no usable ipython_dir is found
add test for gh-669, and ignore nonexistent toy paths in other path tests.
2a8de3c
Evan Patterson
Collaborator

@minrk fixed this, but issue was never closed. Just cleaning up here...

Evan Patterson epatters closed this August 23, 2011
Brian E. Granger ellisonbg referenced this issue from a commit January 10, 2012
Commit has since been removed from the repository and is no longer available.
Brian E. Granger ellisonbg referenced this issue from a commit January 10, 2012
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.