A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-March/086906.html below:

[Python-Dev] Pickler/Unpickler API clarification

[Python-Dev] Pickler/Unpickler API clarification [Python-Dev] Pickler/Unpickler API clarificationGreg Ewing greg.ewing at canterbury.ac.nz
Sun Mar 8 05:55:34 CET 2009
Michael Haggerty wrote:

> Typically, the purpose of a database is to persist data across program
> runs.  So typically, your suggestion would only help if there were a way
> to persist the primed Pickler across runs.

I don't think you need to be able to pickle picklers.

In the case in question, the master pickler would be primed
by pickling all the shared classes, and the resulting pickle
would be stored in the database.

When unpickling, the master unpickler would be primed by
unpickling the shared pickle.

-- 
Greg
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4