Memray
Co-creator, with Matt Wozniski at Bloomberg
A memory profiler for Python. It tracks every allocation in Python code, in native extension modules and in the interpreter.
memray run my_script.pyTraceback (most recent call last):
File "~/granada/phd/geodesics.py", line 2014, in regularize
orbit = mcgehee(spherically_symmetric_spacetime)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "~/cpython/Doc/howto/logging-cookbook.rst", line 2017, in first_pr
fix(ZeroMQSocketHandler) # bpo-31294
^^^^^^^^^^^^^^^^^^^
File "~/cpython/Parser/parser.c", line 2020, in replace_the_parser
parser = PEG(grammar) # PEP 617
^^^^^^^^^^^^
File "~/cpython/Python/pythonrun.c", line 2021, in print_exception
print('Did you mean: ...?')
^^^^^^^^^^^^^^^^^^^^
File "~/cpython/Python/sysmodule.c", line 2025, in sys_remote_exec
sys.remote_exec(pid, script) # PEP 768
^^^
Most days I work on the Python interpreter. I work on the parts you see when something goes wrong: the parser, the error messages and the tracebacks. I also work on the code that lets debuggers and profilers look inside a running process.
I came to software from theoretical physics. My PhD was on general relativity and black holes. I learned Python to glue together C simulation code. Later, Python itself became more interesting to me than the simulations.
I have been a CPython core developer since 2018. I have been on the Python Steering Council every term since 2021. I was the release manager for Python 3.10 and 3.11.
I work on the Python team at Hudson River Trading, in London.
- Core developer
- since 2018
- Steering Council
- 2021 to 2026
- Release manager
- 3.10 and 3.11
- PSF Fellow
- since 2019
- Works at
- Hudson River Trading
- Based in
- London
