Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Do not accept an ipython_dir that's not writeable #669
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.