> You don't. You shouldn't. There's a good reason the functionality exists: It's a breeze for quickly persisting some state without worrying about anything els

> You don't. You shouldn't. There's a good reason the functionality exists: It's a breeze for quickly persisting some state without worrying about anything else. It's not pretty, it's not clean, but it just works (which is arguably a use case Python is very popular for). A sibling comment pointed out that pickled data makes it annoying to deal with eventual schema changes. For sure. But so do other things that go hand in hand with quick-and-dirty approaches. "Probably don't use pickle in production" is something I could get behind, but that would, of course, not be such an inflammatory title.