##// END OF EJS Templates
run_cell returns an ExecutionResult instance...
run_cell returns an ExecutionResult instance gh-7256 asked for a boolean return value from run_cell() for whether code ran successfully. I discussed this with Min, who suggested that given the complexity of run_cell, it should return a result object that can store different pieces of information about what happened. This currently stores `execution_count`, `error_before_exec` (i.e. errors transforming, parsing or compiling the code), `error_in_exec` and `result`. It calculates `success` as a boolean that's true if neither of the error fields are set. Closes gh-7256
Thomas Kluyver -
r19630:0e76a046
Show More
Name Size Modified Last Commit Author
/ IPython / core / tests
2x2.jpg Loading ...
2x2.png Loading ...
__init__.py Loading ...
daft_extension.py Loading ...
nonascii.py Loading ...
nonascii2.py Loading ...
print_argv.py Loading ...
refbug.py Loading ...
simpleerr.py Loading ...
tclass.py Loading ...
test_alias.py Loading ...
test_application.py Loading ...
test_autocall.py Loading ...
test_compilerop.py Loading ...
test_completer.py Loading ...
test_completerlib.py Loading ...
test_debugger.py Loading ...
test_display.py Loading ...
test_events.py Loading ...
test_extension.py Loading ...
test_formatters.py Loading ...
test_handlers.py Loading ...
test_history.py Loading ...
test_hooks.py Loading ...
test_imports.py Loading ...
test_inputsplitter.py Loading ...
test_inputtransformer.py Loading ...
test_interactiveshell.py Loading ...
test_iplib.py Loading ...
test_logger.py Loading ...
test_magic.py Loading ...
test_magic_arguments.py Loading ...
test_magic_terminal.py Loading ...
test_oinspect.py Loading ...
test_page.py Loading ...
test_prefilter.py Loading ...
test_profile.py Loading ...
test_prompts.py Loading ...
test_pylabtools.py Loading ...
test_run.py Loading ...
test_shellapp.py Loading ...
test_splitinput.py Loading ...
test_ultratb.py Loading ...