-
Notifications
You must be signed in to change notification settings - Fork 55
pip install not working from Project Jupyter #54
Comments
@vinomaster, it appears that the problem you are experiencing is related to the conda container not having the correct |
If we're talking try.jupyter.org specifically, keep in mind it allows no external network access. You can try what they have installed, but you can't pull in anything new from the internet at large. Otherwise, it'd become a target for hosting all manner of unsavory content. |
Good point @parente. At this point it is only clear that there is a networking issue w.r.t. installing the library. If the problem is on try.jupyter.org then the networking issue is because of what @parente pointed out in #54 (comment) and clearly there is no resolution to that. If the problem is happening in a separate environment with known external network access using conda for Python2 then the problem is likely that the conda container does not know the correct nameserver as was mentioned in #54 (comment). In either case, my recommendation would be to set up your own venv with Python 2.7 and ipython notebooks and this should resolve the issue. |
Ok tactical workaround - install on a separate python2 env. |
Python3 support is slated to be part of the first stable release 2.0.0. No date is available but we are adding functionality often. So it shouldn't be too far down the road. You can track the effort with #23. |
Moving this to its own issue.
See: #49 (comment)
The text was updated successfully, but these errors were encountered: