-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
After upgrading JupyterLab using pip, I started jupyter-lab from the windows command and got an error. #577
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Did you uninstall the old version first? If yes, did you run your command line in administrator mode? It looks like the problem is with the jupyter server. So I would highly recommend updating the server. which you can also do when you remove the current instillation and re-install it. |
First time I installed JupyterLab in upgrade mode with pip: pip install JupyterLab --upgrade I didn't do it but today I uninstalled JupyterLab, then I installed again as administrator and tried to run it as admin as well getting almost the same: C:\WINDOWS\system32>jupyter-lab versions I have installed of several jupyter apps. jupyter 1.0.0 |
@acuenya are you trying to upgrade jupyterlab Python package or the JupyterLab Desktop application? |
Triage notes: This can be improved in documentation for users who are upgrading. |
I updated JupyterLab with pip
pip install JupyterLab --upgrade
after that I tried to start from Windows PS command as always do: jupyter-lab and got the following error
C:\Users\cueny\AppData\Local\Programs\Python\Python39\lib\site-packages\traitlets\traitlets.py:1872: FutureWarning: ServerApp.preferred_dir config is deprecated in jupyter-server 2.0. Use FileContentsManager.preferred_dir instead
return self._get_trait_default_generator(names[0])(self)
[C 2023-02-13 11:24:56.237 ServerApp] Bad config encountered during initialization: is outside root contents directory
The text was updated successfully, but these errors were encountered: