-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Bad config encountered during initialization: #2875
Comments
Hi Emily, It sounds like you have |
Sure thing. Here they are:
Thanks! |
@bollwyvl, @damianavila, thoughts on the above? |
What is the content of this file? |
I encountered this error : Please share any information on how to resolve this. Thanks
|
@gayathry2612: For what it's worth, I just encountered this error after an upgrade. To fix it, I removed my ~/.jupyter config directory, reinstalled all jupyter-related packages with
and reenabled the one extension I had installed:
You'll also have to reapply any customisations you've made to the config files, but I didn't have any. |
Removing |
This is might Help I SOLVED and wrote about it here There is sometimes that the jupyter_notebook_config.py is missing To create a jupyter_notebook_config.py file, after installing the python , you can use the following command line: |
|
the file is bad,it is a little problem,so easy,thanks! |
Removing ~/.jupyter did not fix the issue for me |
This can also occur if you have extensions installed in your global jupyter lab/notebook configuration, but not the underlying python packages installed in your Conda environment. In my case, it was jupyter-fs messing things up, which saves a configuration .json in .jupyter, and tries to read it. But without the jupyter-fs Python package, it causes this error on start-up. |
I was learning and practicing anaconda on cloud and this happened Bad config encountered during initialization: The 'kernel_spec_manager_class' trait of <notebook.notebookapp.NotebookApp object at 0x7f238ef2e290> instance must be a type, but 'nb_conda_kernels.CondaKernelSpecManager' could not be imported |
I am trying to run miniconda of virtual Ubuntu server and access Jupyter notebook remotely, and I'm also having this error. What should my exact steps be to install and run Jupyter on miniconda? UPD Worked for me after I recreated my working environment and did |
As other people noted, deleting the
It will return the list of possible config files, and tell you which file is loaded. In my case :
Then, simply delete the appropriate config file, according to the output, and you should be able to reset the config. |
The solution suggested by @JPapir worked for me. |
When I try to launch Jupiter Notebook from the command line or from Anaconda Navigator I get the following error:
[C 13:09:45.091 NotebookApp] Bad config encountered during initialization:
[C 13:09:45.104 NotebookApp] The 'kernel_spec_manager_class' trait of <notebook.notebookapp.NotebookApp object at 0x101ca3278> instance must be a type, but 'nb_conda_kernels.CondaKernelSpecManager' could not be imported
I can run Jupiter Notebook from other Python environments but not from root. I would really like to just be able to launch the notebook using the default version of Python on my machine. Currently this is 3.6.2.
Many thanks,
Emily
The text was updated successfully, but these errors were encountered: