xunter is to tracing and profiling xonsh shell using hunter. Time tracking is on board.
If you like the idea click ⭐ on the repo and tweet.
Install xunter into the environment where xonsh you want to trace resides.
pip install xunter
# or: pip install git+https://github.com/anki-code/xunterXunter is working as drop-in replacement of xonsh with additional arguments:
xonsh --no-rc -c "2+2"
xunter --no-rc -c "2+2" ++depth-lt 5
# ^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^
# xonsh xunterSimple examples:
xunter --no-rc -c "2+2" ++depth-lt 10
xunter --no-rc ++depth-lt 5 ++output /tmp/22.xun
xunter --no-rc -c '2+2' ++filter 'Q(filename_endswith="main.py")'To set ++filter read about filters
and take a look into the cookbook.
Use ./playground/trace.py to experiment with the tracing filters and understand how it works.
mkdir -p ~/git/ && cd ~/git/
git clone git+https://github.com/xonsh/xonsh
cd xonsh
xunter --no-rc -c '1+1' ++cwd ++filter 'Q(filename_has="procs/")' ++output /tmp/out.xun
# Trace ./xonsh
# In another terminal:
tail -f /tmp/out.xunxunter --no-rc -c 'echo 1' ++filter 'Q(filename_has="specs.py")' ++output /tmp/specs.xun
cat /tmp/specs.xun | grep run_subproc
# [...]/site-packages/xonsh/procs/specs.py:910:run_subproc
# <= xonsh/built_ins.py:206:subproc_captured_hiddenobject
# <= <string>:1:<module> <= xonsh/codecache.py:64:run_compiled_code
# <= xonsh/codecache.py:218:run_code_with_cache
# <= xonsh/main.py:519:main_xonsh
# <= xonsh/main.py:470:main
# <= xunter/xunter:91:<module>
# - time_sec=[0.1505]
# Don't forget about xonsh`s awesome macro call:
xunter --no-rc -c 'echo 1' ++printer call ++filter! Q(filename_has="specs.py"),Q(function="run_subproc")# These `filename` filters will be applied to the code that executed at the end.
# i.e. `filename="a.py"` will filter `a.py:func <= b.py:func <= c.py:func`
# but `c.py:func <= a.py:func <= b.py:func` case (`a.py` in the middle) wont be filtered.
filters = [
'~Q(filename_has="prompt_toolkit/")',
'~Q(filename_has="prompt/")',
'~Q(filename_has="ptk_shell/")',
'~Q(filename_has="pygments")',
'~Q(filename_has="_distutils_hack")',
'~Q(filename_has="lazyasd")',
'~Q(filename_has="environ")',
'~Q(filename_has="layout")',
]
xunter --no-rc ++filter @(','.join(filters)) ++output /tmp/1.xun
# Run in another terminal to monitor the activity:
tail -f /tmp/1.xun # | grep -i funcxunter --no-rc -c 'echo 1' ++time-sec-gt 0.1 ++depth-lt 2
# ... - time_sec=[1.3710]xunter --no-rc -c "2+2" ++depth-lt 10 ++printer stack ++output /tmp/22.xun
xunter2excel /tmp/22.xunIf you see the unexpected exceptions try to install xonsh from the main branch first:
xpip install -U --force-reinstall git+https://github.com/xonsh/xonsh
# restart xonsh
xunter ++output /tmp/xonsh.xun- samply - Command-line sampling profiler. Profiling xonsh.
- xonsh-cheatsheet
- xonsh-install
- How to debug xonsh interactively in IDE PyCharm
- By putting
import ipdb; ipdb.set_trace()into any place of code you can investigate the environment interactively. - xonsh builtin
trace
