JIT and GIL removal are not even my most anticipated Python 3.13 features
blog.vslira.net
blog.vslira.net
- fleshed out modules: functools, itertools -- love them; also bisect, collections, decimal, math, random, and type aliases
- enhanced the dictionary and set types, used by 100% of programs
His talks are high-energy and very useful. I just found one on "Pro tips for writing Unit Tests" <3 -- https://www.youtube.com/watch?v=jSIsyMd2-RY
These types of serialisation are a technical debt from day one. There are countless stories of ecosystems doing a very painful migration to get away from it. See java, or recently the ML model files trying to go to safetensors etc.
If you only want to store bytes, the safe way to do so is to use the dbm module directly, which doesn't pickle/unpickle the data you provide.
I suppose if a remote store is involved then the attack would be easier: you don’t need to hack the server running my code, just the DB/KV-store/whatever storing the pickles. Is that a common use case though? It seems like JSON and other dedicated formats are vastly more common for serializing data across machine boundaries.
Depending on the use case it might be better to just use the dbm module directly.
Cool to see it supported ootb as a dbm backend.