Skip to content
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

Using python-jl for Jupyter Notebook #2613

Open
calvinp0 opened this issue Feb 20, 2024 · 2 comments
Open

Using python-jl for Jupyter Notebook #2613

calvinp0 opened this issue Feb 20, 2024 · 2 comments
Labels
stale stale issue/PR as determined by actions bot

Comments

@calvinp0
Copy link
Member

Hi, is it possible to run packages, like RMS, in Jupyter Notebook? Currently, when I use rmg_env as the kernel (linking to python) it cannot do

from pyrms import rms

I assume this is to do with importing PyCall. Is there a way to use python-jl instead of python for the kernel in Jupyter?

@mjohnson541
Copy link
Contributor

You're correct that the issue is the kernel. If you run jupyter --paths, go to any of the data paths (using the rmg_env one might feel like instinctively the right choice, but that one will be deleted if you regenerate the rmg_env so a more general one will likely make your life easier) and then to kernels. You should be able to mostly copy a python kernel folder to make a python-jl kernel folder. The only modification that needs made to the copied python kernel is to change the path in the kernel.json to the path to the appropriate python-jl (which you can get running which python-jl).

Copy link

This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days.

@github-actions github-actions bot added the stale stale issue/PR as determined by actions bot label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale stale issue/PR as determined by actions bot
Projects
None yet
Development

No branches or pull requests

2 participants