NordicHPC / NordicHPC/envkernel

How might it be possible to add IJulia to `KNOWN_KERNELS`?

Open
#3 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
28
Forks
2
Avg merge
17m
Merged PRs (30d)
1

Description

As far as I can tell, the value of argv in a kernel.json corresponding to an IJulia installation should be:

["/path/to/binary/julia", "-i", "--startup-file=yes", "--color=yes", "/path/to/install/location/of/IJulia/kernel.jl", "{connection_file}"]

Comparing this to what's already in envkernel.py, it seems like adding IJulia as a "known kernel" would amount to something similar to:

KNOWN_KERNELS = {
...
},
'ijulia' : {
'language' : 'julia',
'argv' : ['julia',
           '-i',
           '--startup-file=yes',
           '--color=yes',
           'kernel.jl',
           '{connection_file}'],
}
}

However, the command seems to require knowing the location of the file kernel.jl (corresponding seemingly to the install location of IJulia), and the above doesn't seem like it would fit with that.

I wanted to submit a PR along these lines, but I'm not sure how to deal with the issue of the kernel.jl file's location to make a PR that would actually work.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read envkernel.py around KNOWN_KERNELS and compare its kernel.json handling with the IJulia argv shown in the issue. Investigate how the installed kernel.jl path can be resolved; done means an ijulia known-kernel entry can launch an IJulia installation without an unavailable hard-coded path.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia, jupyter, python
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.