#342: Try to recover as intelligently as possible if user calls magic(). #352
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.
This was annoying me from the perspective of force-of-habit typing quit() (system install at the lab of IPython 0.8.3 (!!!!!) requires it) but in general, people typing some_magic() with automagic on and expecting results might be awfully surprised by the NameError that results.
This attempts to address the problem in the following way:
----> %some_magic
so that the user has some clue that what he typed was interpreted as a magic but that the subsequent parenthesized arguments were ignored.The result looks something like this:
Ideally then, individual magics, if they require arguments, will complain about not receiving them, and in the process demonstrate their usage with the correct
%foo bar baz
way of calling them.This pull request replaces #345.