-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
IJulia Installation on Windows #363
Comments
…yter is not in path as suggested in jupyter/notebook#448
…yter is not in path as suggested in jupyter/notebook#448
I have proposed a fix in #364 could you check if it works? |
Simply patching those 2 lines didn't seem to work for me: I ran Windows Powershell with administrator and did "jupyter: kernelspec is not a Jupyter command"
|
Ok. Have you tried the orginal build script after |
Yep, it yields the error above (kernelspec is not a Jupyter command). Do I need to be using the dev branch of Jupyter notebook for kernelspec to show up? |
Sorry the comment split the line unfortunate it is |
Unfortunately, that doesn't work either :/
|
Do the command work in cmd instead of powershell? |
tried that, doesn't work either.
Strangely enough, running
|
Hmm. I am indeed confused now. I think the only resolution to this is to wait for jupyter/jupyter_core#62 or downgrade to IPython3. Alternative you could let IJulia use the Conda package which can be done by: julia> ENV["JUPYTER"]=""
julia> Pkg.build("IJulia") |
If |
It sounds like what minrk describes here, jupyter/notebook#448 (comment) where jupyter/jupyter_core#62 is the PR for fixing the issue. |
I had the very same issue, using
If I try to
My understanding is that although As a temporary workaround, I replaced line 101 of build.jl with: run(`python C:\\Anaconda\\Scripts\\$jupyter-kernelspec install --replace --user $juliakspec`) and ran I still don't get it and I'm certain there is a cleaner solution. |
@n-s-k, does |
julia> run(`jupyter --version`)
4.0.6
julia> run(`jupyter-console --version`)
4.0.2
julia> run(`jupyter-notebook --version`)
4.0.5
julia> run(`jupyter-kernelspec --version`)
ERROR: could not spawn `jupyter-kernelspec --version`: no such file or directory (ENOENT)
in _jl_spawn at process.jl:217 (repeats 2 times) |
What is Oh, from above I guess it is a Python file? (But doesn't end with |
On my Mac,
but I guess Windows doesn't know how to spawn this. |
On Windows, #!C:\Anaconda\python.exe
from jupyter_client.kernelspecapp import KernelSpecApp
def main():
KernelSpecApp.launch_instance()
if __name__ == '__main__':
main() yep... a python script and Windows is clueless. |
Okay, this should be a straightforward fix. We just need to find the correct path of |
Okay, it should be fixed now. Please do |
Confirmed. |
This works for me too. Thanks! On Wed, Sep 30, 2015 at 2:44 PM, n-s-k [email protected] wrote:
|
Great, tagged as IJulia 1.1.2. |
I'm hitting this with the latest tag.
|
Hmm, do we need a similar fix on windows to get |
I believe several of these issues (esp #368) were caused by improper packaging of entrypoints in the Jupyter projects on Windows. Most of the entrypoints were fixed relatively promptly during the summer, but |
Thanks, @minrk. We will keep the workarounds in for quite some time, to support older installations, but it is great to hear that this has been fixed. |
This proposed change amends and extends the previously included (so-called) hacks for Windows that were added for issue JuliaLang#363 (that are waiting on issue JuliaLang#448 for the jupyter project). These changes allow for IJulia to work a version of Python that has been downloaded from python.org, where jupyter was pip installed with a version recent enough to include jupyter-kernelspec.exe and jupyter-notebook.exe, and where the end user has set the JUPYTER environment variable either at the system level or in ENV within their Julia session prior to building IJulia via Pkg.build. If the issues that led to the discussion in JuliaLang#363 and jupyter issue JuliaLang#448 have been addressed, then the changes in this commit and PR can likely be ignored.
* Additional workarounds for jupyter-kernelspec.exe This proposed change amends and extends the previously included (so-called) hacks for Windows that were added for issue #363 (that are waiting on issue #448 for the jupyter project). These changes allow for IJulia to work a version of Python that has been downloaded from python.org, where jupyter was pip installed with a version recent enough to include jupyter-kernelspec.exe and jupyter-notebook.exe, and where the end user has set the JUPYTER environment variable either at the system level or in ENV within their Julia session prior to building IJulia via Pkg.build. If the issues that led to the discussion in #363 and jupyter issue #448 have been addressed, then the changes in this commit and PR can likely be ignored. * Adding changes based on line note suggestions Addressing the line notes, #416 (comment) and #416 (comment) added by @stevengj * Correction based on line note Updating based on [comment](#416 (comment))
On Windows 7, 64-bit. Here is the error: INFO: Downloading miniconda installer ...
INFO: Installing miniconda ...
===============================[ ERROR: IJulia ]================================
LoadError: could not spawn `'C:\Users\bsouthwood\.julia\v0.4\Conda\deps\usr\installer.exe' /S /AddToPath=0 /RegisterPython=0 '/D=C:\Users\bsouthwood\.julia\v0.4\Conda\deps\usr'`: unknown error (UNKNOW
N)
while loading C:\Users\bsouthwood\.julia\v0.4\IJulia\deps\build.jl, in expression starting on line 35 |
@bsouthwood, that should be reported at Conda.jl |
Apologiea, i'm a noob.. I checked line 35 of the build.ml file and it contained a jupytyr variable so i thought it was related to this threas. |
It looks like IJulia.jl is using the globally installed jupyter/ipython (rather than one locally installed from Conda.jl). This means that if you have ipython installed but not jupyter (specifically jupyter_client, though with just that |
@bsouthwood, to simplify installation, do |
Thanks. |
I am using Windows 10 and Anaconda with julia-0.5.0. I previously had IJulia installed and working, but then somehow calling Pkg.update() broke my installation.
Here is the error message:
Installing julia kernelspec julia-0.5
===================================================[ ERROR: IJulia ]====================================================
LoadError: could not spawn
jupyter-kernelspec install --replace --user julia-0.5
: no such file or directory (ENOENT)while loading C:\Users\eric.julia\v0.5\IJulia\deps\build.jl, in expression starting on line 101
====================================================[ BUILD ERRORS ]====================================================
WARNING: IJulia had build errors.
Pkg.build("IJulia")
deps/build.jl
scriptINFO: Package database updated
Running
Pkg.build("IJulia")
produced the same error.The text was updated successfully, but these errors were encountered: