ModuleNotFoundError: No module named 'jupyter_server.contents' #7048
Labels
Comments
|
@afshin @kevin-bates @blink1073 FYI since you were involved in the original PR |
|
We've tracked the issue down to the traitlets package. With 5.10.0 we see this issue, if we downgrade to 5.9.0 then it goes away. |
|
This is a typo because it should be |
This was referenced Sep 15, 2023
|
@Charles-Gagnon Thanks for opening the issue. I am also getting the same error when I run Downgrading |
|
Related: the buggy / breaking version of Note that |
7 tasks
|
Verified that fix released in 6.5.6 resolves this issue. Thanks! |
4 tasks
grzenkom
added a commit
to grzenkom/lang-chain-qa
that referenced
this issue
Sep 19, 2023
antoniivanov
added a commit
to vmware/versatile-data-kit
that referenced
this issue
Sep 19, 2023
Latest release of traitlets (5.10) is breaking jupyter server - jupyter/notebook#7048 which is causing jupyter server to fail to start So we are pinning temporarily to 5.9 to fix that.
antoniivanov
added a commit
to vmware/versatile-data-kit
that referenced
this issue
Sep 19, 2023
Latest release of traitlets (5.10) is breaking jupyter server - jupyter/notebook#7048 which is causing jupyter server to fail to start So we are pinning temporarily to 5.9 to fix that.
|
While the fix is good, perhaps the end of the traceback (about |
Merged
5 tasks
yosh-matsuda
pushed a commit
to fixstars/amplify-examples
that referenced
this issue
Sep 29, 2023
6 tasks
bjhardcastle
added a commit
to AllenInstitute/npc_sessions
that referenced
this issue
Oct 19, 2023
Python 3.9 with JupyterLab 3.6.1 starter environment uses `notebook 6.5.5`, which is incompatible with `traitlets 5.10.0` see jupyter/notebook#7048 - we don't have `notebook` as a dependency, so we'll just cap the version of `traitlets`
helperbot-recidiviz
pushed a commit
to Recidiviz/pulse-data
that referenced
this issue
Dec 20, 2023
…z/recidiviz-data#25941) ## Description of the change More info here- jupyter/notebook#7048 and here- https://recidiviz.slack.com/archives/CJDCVR2AY/p1695834530847029 ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#25939 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant --------- Co-authored-by: Helper Bot <helperbot@recidiviz.org> GitOrigin-RevId: 909be7effe1526943eda06161d593087a8d9ce77
digital-thinking
added a commit
to digital-thinking/hello-ltr
that referenced
this issue
Jan 16, 2024
|
It didnt work for me... My conda list: Anaconda 2023.09 in Ubuntu 22.04 |
wrigleyDan
pushed a commit
to o19s/hello-ltr
that referenced
this issue
Feb 12, 2024
|
@ejgutierrez74 I faced a similar problem when the installation of an old version did not fix the problem with pip freeze seeming to confirm the right version being there. The problem was that pip freeze in my case used package version from different sites-packages location than used by tljh. TLJH used directory /opt/tljh/user/lib/python3.9/site-packages/traitlets |
|
I dont know after upgrading all libraries with conda update conda, and then uninstall Anaconda Tools, seems that with older versions, now its again working, with jupyter lab and jupyter notebook in the main page ready to be launched.....Perhaps and upgrade bug/error... Probably never guess if not other people facing same problem...Id say its updating problem with Anaconda Tools, anaconda tools is not installed by default...so jupyter lab and jupyter network are not shown in main navigator page ( although they are installed in the environment). Then install anaconda tools make them appear again....and if you uninstall anaconda tool, they remain in the main page...This is my investigation at least... |
after installing traitlets==5.9.0 everything work fine |
|
after installing traitlets==5.9.0 everything work fine |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: 6.5.5
I've recently started seeing this error when starting up a Notebook app with package version 6.5.5
It seems to be caused by #5957. In it there's two similar lines in different files
https://github.com/jupyter/notebook/pull/5957/files#diff-805382c95cfca475b5339bcb7ccd1ee13e9326a9d15adf3a6419d32cb38024d5R1394
This has the type specified as
jupyter_server.contents.services.managers.ContentsManager(which doesn't seem to be a valid path)while in https://github.com/jupyter/notebook/pull/5957/files#diff-ba803f92fc3fea5ab9ef22c8064d587d629353f5c9beaa33a809d70dad8cea80R34
it's specified as
jupyter_server.services.contents.manager.ContentsManagerNot sure if I'm missing something, or if this was just a typo but I confirmed that if I go in and manually change the "wrong" name in $(Python)\site-packages\notebook\notebookapp.py to the other name then it seems to start up and everything is fine.
The text was updated successfully, but these errors were encountered: