Better error messages for common magic commands. #2329
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Print a helpful message when the user calls a magic command with a missing argument, rather than a long traceback.
All magics in the list produce a useful error message when called without any arguments.
|
looks ok to me.
is a good idea. |
|
merging. |
Carreau
added a commit
that referenced
this pull request
Aug 25, 2012
Better error messages for common magic commands.
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
Better error messages for common magic commands.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Print a helpful message when the user calls a magic command with a missing argument, rather than a long traceback.
In addition, I have removed the 'protected' magic list from qtconsole .. these are the magic whose name shows up like
%load?. I think it's visually confusing to have some magics show up with a question mark, and it seems irrelevant if running the magic command prints a short usage error message. One small issue is this might prevent the discovery of the%magic?syntax for getting help. Perhaps we should catchUsageErrorinrun_line_magicandrun_cell_magicand suggest the user run%{magic_name}?for help.