Host on PyPI

Is it possible to host this as a pip package on PyPI so that a user can pip install it and it will be available to their Jupyter notebook kernels?

A quick pip search reveals existing kernels that do something like this:

coq-jupyter (1.4.0)                          - Coq kernel for Jupyter
jupyter-sql (0.1.0)                          - Simple SQL kernel for Jupyter
jupyter-kernel-singular (0.9.8)              - A Jupyter kernel for singular
jupyter-kernel-polymake (0.16)               - A Jupyter kernel for polymake
macaulay2-jupyter-kernel (0.6.7)             - Jupyter kernel for Macaulay2
jupyter-kernel-gap (0.15)                    - A Jupyter kernel for GAP
jupyter-fortran-kernel (0.1.0)               - Minimalistic Fortran kernel for Jupyter
sorna-jupyter-kernel (0.1.3)                 - Sorna Jupyter Kernel Integration
jupyter-kernel-mgmt (0.3.0)                  - Jupyter protocol implementation and client libraries

Clearly, there is not a standardized naming scheme. However, jupyter-kernel-chapel seems like the most popular option.

@ben-albrecht I will host it in pip.

@ben-albrecht I have hosted it in PyPI.
For installing you can follow the readme or

pip3 install jupyter-kernel-chapel
install_chapel_kernel --user

Nice! Is it possible for the setup.py to do the install_chapel_kernel step automatically or is it separate for a specific reason?

Taking a glance at the fortran kernel repository, it looks like they require a similar post-installation command: jupyter-kernelspec install fortran_spec/.

Perhaps this is the norm for installing kernels?

Hey @ben-albrecht, Actually we are doing it internally rather than asking the user to do that

jupyter_kernel_chapel/jupyter-kernel-chapel/install_chapel_kernel

Line 33 in ce54fb7

    
           KernelSpecManager().install_kernel_spec(td, 'chapel', user=user, replace=True, prefix=prefix)

But if you will check fortran is using json file and calling it from outside to install it.

Actually we are doing it internally rather than asking the user to do that

Oh, so can a user skip this step?

> install_chapel_kernel --user

I'll try it out myself when I get a chance.

@ben-albrecht No, I don't think so.
But I will try to find out some other ways for this.

@ben-albrecht I have made changes and now

> install_chapel_kernel --user

is not needed.

That worked for me! Thanks!