3 ms·
Isn't this now irrelevant since Pep 553[0] (adding breakpoint()) was introduced in python 3.7? If not, it's not very clear how this differs from breakpoint().
by craftyguy 8y ago
Isn't this now irrelevant since Pep 553[0] (adding breakpoint()) was introduced in python 3.7?
If not, it's not very clear how this differs from breakpoint().
0) https://www.python.org/dev/peps/pep-0553/ https://www.python.org/dev/peps/pep-0553/
- BugsJustFindMe 8y agoYes, in Py3.7 which everyone uses by now, although it is very annoying to have to then type "interact" after hitting a breakpoint to actually get to the interactive shell. This appears to just be a macro for code.interact(local=dict(globals(), **locals())) And it doesn't pretend to be otherwise. But this lib is still a fantastic idea, because that code.interact line is obnoxious as hell to type when you need it and breakpoint doesn't actually get you to the shell.
- imauld 8y agoI mean: import pdb; pdb.set_trace() is totally a thing. And ipdb is even better.