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
Relative imports broken in the notebook (Windows) #4317
Comments
Odd, I can't see how that would have affected import machinery. Can you give an example of a failing case? |
Weird. It only happens on my default profile, not in a fresh profile (I have a few startup scripts). Let me investigate further... |
Very weird. No startup script = no problem. Add an empty .py file in Test notebook:
|
Hmm, I see that as well. Weird. It's not actually a relative import, though - it's an absolute import, it's just that the CWD isn't getting added to sys.path, for some reason. |
OK, after some frenzied debugging with frequent cries of 'what?', Min has a fix on the way. |
recent change caused initial sys.path to lose '' as the first element in the notebook. closes ipython#4317
recent change caused initial sys.path to lose '' as the first element in the notebook. closes ipython#4317
It seems like relative imports do not work anymore in my notebooks since 6590fa5.
I'm on Windows 8 64 bits, Python 2.7.5.
The text was updated successfully, but these errors were encountered: