[New-bugs-announce] [issue13426] The Python Standard Library >> 11. Data Persistence

Nebelhom report at bugs.python.org
Fri Nov 18 12:29:59 CET 2011


New submission from Nebelhom <nebelhom at googlemail.com>:

------------------------------
Python v3.3a0 documentation >> The Python Standard Library >> 11. Data
Persistence

Section 11.1 pickle module

#1
11.1.3. Module Interface

exception pickle.UnpicklingError

   Error raised when there a problem unpickling an object, such as a data corruption or a security violation.
   It inherits PickleError.

TYPO: Error raised when there IS a problem unpickling an object

------------------------------
#2
11.1.3. Module Interface

persistent_load(pid)

   Raise an UnpickingError by default.

TYPO: Should be "Unpick"l"ingError" as wrtten earlier in the section

--------------------------------
#3
11.1.4 What can be pickled and unpickled

Note that functions (built-in and user-defined) are pickled by >>fully
qualified<< name reference, not by value.
This means that only the function name is pickled, along with the name of module the function is defined in.

TYPO: along with the name of "THE" module the function is defined in.

--------------------------------
#4
11.1.5.1. Persistence of External Objects

In Windows XP SP3, example does not work out of the box as sqlite3 is not included when compiling python3.3a following the Getting Set Up directions in the Developer's Guide

Is this an issue?

Code works in Ubuntu 10.04 lucid.

When run from Terminal, it gives the following output:

Pickled records:
[MemoRecord(key=1, task='give food to fish'),
 MemoRecord(key=2, task='prepare group meeting'),
 MemoRecord(key=3, task='fight with a zebra')]
Unpickled records:
[MemoRecord(key=1, task='learn italian'),
 MemoRecord(key=2, task='prepare group meeting'),
 MemoRecord(key=3, task='fight with a zebra')]


 Should that not be given afterwards as a reference to the user, so that
(s)he knows, that the code is right?

--------------------------------
#5
11.1.6 Restricting Globals

Thus it is possible to either forbid completely globals

NOTE: should be "either completely forbid globals"

--------------------------------

----------
assignee: docs at python
components: Documentation
messages: 147851
nosy: Nebelhom, docs at python
priority: normal
severity: normal
status: open
title: The Python Standard Library >> 11. Data Persistence
versions: Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13426>
_______________________________________


More information about the New-bugs-announce mailing list