-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
CommandError: Could not load shell runner: 'IPython Notebook'. #1835
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
Comments
I was able to temporarily fix that by using old version of
|
also getting this issue, and it continues to present after downgrading jupyer_client ... I have the following:
is this an issue with a notebook release? running on Mac M1 Pro |
I believe the issue is due to changes made in the recent quite large notebook version change from
|
yes, |
I confirm what @chbroecker said. For me, it worked (keeping notebook version 6) using
|
I solved the issue downgrading notebook with this command pip install notebook==6.5.6 Then using the command python manage.py shell_plus --notebook work well for me. |
PyCharm or VSCode can use Notebook 7 out of the box. For Django, I only need to set the project settings. This is a shame Notebook 7 cannot run from the terminal (it should open a browser) import os
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'myproject.settings')
os.environ["DJANGO_ALLOW_ASYNC_UNSAFE"] = "true" |
There is a workaround. Instead of running # First run:
import os, sys
import django
PROJECTPATH = '/path/to/your/djangoproject'
sys.path.insert(0, PROJECTPATH)
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "djangoproject.settings")
os.environ["DJANGO_ALLOW_ASYNC_UNSAFE"] = "true"
os.chdir(PROJECTPATH)
django.setup()
# and now you can run any of your code, e.g.
from django.conf import settings
print(settings.DATABASES) |
I had the same issue. I solved it by downgrading these packages:
|
I am using django 4.2 abd python 3.10.
OS: Windows WSL (Linux subsystem on a windows machine)
This works:
But not this:
Error:
pip list:
The text was updated successfully, but these errors were encountered: