On launching jupyter notebook from linux - created Environment - Facing attached problem

Need steps and procedure to avoid the problem of launching Jupyter-notebook at event later times.

Unexpected behavior observed with launching of “jupyter-notebook and jupyter notebook” command:
box@box-virtual-machine:~/python_programs$ jupyter notebook
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/notebook/traittypes.py”, line 232, in _resolve_classes
klass = self._resolve_string(klass)
File “/home/box/.local/lib/python3.10/site-packages/traitlets/traitlets.py”, line 2018, in _resolve_string
return import_item(string)
File “/home/box/.local/lib/python3.10/site-packages/traitlets/utils/importstring.py”, line 31, in import_item
module = import(package, fromlist=[obj])
ModuleNotFoundError: No module named ‘jupyter_server.contents’

box@box-virtual-machine:~/python_programs$ pip list | grep jupyter*
jupyter 1.0.0
jupyter_client 8.5.0
jupyter-console 6.6.3
jupyter_core 5.5.0
jupyter-events 0.9.0
jupyter-lsp 2.2.0
jupyter_server 2.10.1
jupyter_server_terminals 0.4.4
jupyterlab 4.0.9
jupyterlab-pygments 0.2.2
jupyterlab_server 2.25.0

echo -e "import sys\nfor path in sys.path:\n\tprint(path)" | python3 | sed '/^ *$/d' | while read path; do echo "${path}"; find "${path}" -type f -name '*jupyter_server*'; done

இந்த கமாண்டை இயக்கி வரும் தகவலை பகிரவும்.

$ echo -e “import sys\nfor path in sys.path:\n\tprint(path)” | python3 | sed ‘/^ *$/d’ | while read path; do echo “${path}”; find “${path}” -type f -name ‘jupyter_server’; done
find: ‘/usr/lib/python310.zip’: No such file or directory

==> Above is the output of the shared SHELL commands

Look up here :

It is due to problem in traitlets module latest version. Work around is to revert traitlets from 5.10.0 to 5.9.0

Traitlets is a pure Python library enabling:

the enforcement of strong typing for attributes of Python objects (typed attributes are called “traits”);
dynamically calculated default values;
automatic validation and coercion of trait attributes when attempting a change;
registering for receiving notifications when trait values change;
reading configuring values from files or from command line arguments - a distinct layer on top of traitlets, so you may use traitlets without the configuration machinery.

After reverting from 5.10.0 to 5.9.0 , jupyter notebook got launched

thank you for resolving issues.