Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Command not found will no longer traceback
Previously, when a command was not found, Jupyter printed a traceback on the user: $ jupyter foobar Traceback (most recent call last): File "/usr/bin/jupyter", line 33, in <module> sys.exit(load_entry_point('jupyter-core==4.6.3', 'console_scripts', 'jupyter')()) File "/usr/lib/python3.9/site-packages/jupyter_core/command.py", line 247, in main command = _jupyter_abspath(subcommand) File "/usr/lib/python3.9/site-packages/jupyter_core/command.py", line 133, in _jupyter_abspath raise Exception( Exception: Jupyter command `jupyter-foobar` not found. Generally, I believe users should only see tracebacks when they are debugging stuff or when there is an unexpected "crash". In Fedora, such traceback is detected as crash by the automatic bug reporting tool. Now, an error message is printed to stderr instead to provide a better UX. Fixes #211
- Loading branch information