hipikat, 14 days ago

@glyph it's a first-line go-to for me for Python shells spawned from pdb

(so less likely to make it to a commit than even a breakpoint() statement, but for developing a module without restarting the whole process, idk how people live without it!)

matt, 14 days ago

@glyph I think the last time I called it was when it was a built-in in Python 2.

glyph, 14 days ago

@matt if I'm being honest I just found out it's no longer a built-in 😅

(Although I think I have imported it from six.moves.reload before.)

xgranade, 14 days ago

@glyph I've heard of it before and its mere mention makes me run screaming.

glyph, 14 days ago

@xgranade would you feel like it were more fun if it were called "treat_module_as_jupyter_cell"

xgranade, 14 days ago

@glyph Fun is... a word. All joking aside though, 100% the uses I've run into for reload have been from Jupyter, so a name like that would help communicate the usecase more clearly?

glyph, 14 days ago

@xgranade the sparse documentation here doesn't quite communicate the depth of the nightmare, but I assure you that this one is even more fun https://docs.twisted.org/en/stable/api/twisted.python.rebuild.html#rebuild

xgranade, 14 days ago

@glyph Having seen the internals of IPython's deep_reload, I am not even slightly surprised.