[disgruntledphd2]

This bug basically hits people who run long lived code sessions with large objects (i.e. data people).

I've hit it in both R and Python in interactive sessions. Otherwise it's generally a non issue.

I can definitely see this being helpful, particularly for the intended context. It would also be useful when you need to move notebook code to a different environment.

[RadiozRadioz]

Completely. I interact with data people sometimes at work. There are bespoke one-of-a-kind venvs and giant notebooks everywhere. But that's okay. They don't have our job, it is not their job to build robust & properly deployed software. They know how to do their thing and we shouldn't lecture them on how to do it the "proper" way. Because I sure don't know how to do what they do - Pandas & matplotlib take me hours of googling to do anything.

I completely see the value in this tool for a particular style of programming.

[dleeftink]

I don't think the issue is telling someone how to do their jobs, but that when it comes to it, we are not properly communicating our stack preferences at all. Online we do, sure, but let's not shy away from having these discussions in the open. There is much to learn from each other's best and worst practices.