##// END OF EJS Templates
Robustness fixes in test suite machinery....
Robustness fixes in test suite machinery. Added a module-level INSTALLED flag, which can be set to false if the test suite is being run in-place (without ipython having been installed at all). This is because how we call and import things must be done differently depending on whether the code is installed or is being run in-place. The only ones that can know this reliably are the entry-point scripts, so those are responsible for setting this flag. Also made the code that validates ipython in subprocesses report errors better, by checking stderr for errors before validating stdout output, as anything on stderr will be likely informative of the real problem.

File last commit:

r2118:ec9810f7
r2494:c8938204
Show More
run_ipy_in_profiler.py
22 lines | 603 B | text/x-python | PythonLexer
/ tools / run_ipy_in_profiler.py
"""XXX - What exactly is the use of this script?
I (fperez) tried it quickly and it doesn't work in its current form. Either it
needs to be fixed and documented or removed.
"""
import cProfile as profile
import sys
#import profile
def main():
import IPython.ipapi
print "Entering ipython for profiling. Type 'Exit' for profiler report"
IPython.ipapi.launch_new_instance()
if len(sys.argv) == 1:
profile.run('main()', 'ipython_profiler_results')
import pstats
p = pstats.Stats(len(sys.argv) >1 and sys.argv[1] or 'ipython_profiler_results')
p.sort_stats('time').print_stats(30)