pickling

For example pickling [2] library uses macros to statically generate highly efficient serialisation and deserialisation boilerplate.

But even just things like pickling a Python object is too onerous for Python itself.

IPython notebook; the need to structure your code to avoid pickling errors; etc.

Think Scala Pickling by Sara Miller at TypeSafe looks excellent for serialization needs.

Counterpoint: All the rails security exploits, python pickling and sql injection issues.

This is way more commendable than say cutting cows in half or pickling sharks in formaldehyde (just to name another two ridiculous art fads).

For instance pickling, home preserves, raising your own chickens, etc.

The sa[fn]e alternative to pickling your objects is to write your data into a well defined file format and read it back with stringent input checks.

A solution to the irritating pickling behaviour of multiprocessing.

What STM (as I understand from blog posts from the pypy team) is that it provides real threading without having to worry about pickling.

Almost always when pickling we're only interested in one aspect of security that is integrity: what we put in is what we get out.

Koreans have a different habit, a focus on long-term preservation of vegetables via pickling and fermentation (not quite as common in China), making out-of-season foods a more normal thing.

An interesting tidbit - the Mozart/Oz team invented "pickling" before it caught on with Python.

I see things other than quirky "fun" tasks like pickling beets (?!) as also a valuable part of a regular life.

By which I mean, give the process everything it needs to get the resources on "its" side (thus avoiding the pickling), and then let it process stuff until it's gotten back to some serializable base object that it can finally return.