Message199467
| Author |
pitrou |
| Recipients |
barry, christian.heimes, kristjan.jonsson, pitrou, serhiy.storchaka, vstinner |
| Date |
2013年10月11日.12:13:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1778174014.69013295.1381493606914.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to |
<1381493074.68.0.971227164202.issue19219@psf.upfronthosting.co.za> |
| Content |
> In fact, using 'marshal' as a cheap and fast pickler for builtin types
> is actually a good idea because it has no side effects like invoking
> code.
It's an unsupported use case. The marshal docs are quite clear:
"""Therefore, the Python maintainers reserve the right to modify
the marshal format in backward incompatible ways should the need
arise. If you’re serializing and de-serializing Python objects,
use the pickle module instead [...]"""
So, it's a "good idea" as long as you're willing to deal with the
consequences :-) |
|