/snap/core22/2437/usr/lib/python3.10/__pycache__
Edit: /snap/core22/2437/usr/lib/python3.10/__pycache__/shelve.cpython-310.pyc (9492B)
o
p̦ip! @ s d Z ddlmZmZmZ ddlmZ ddlZg dZ G dd dej
j Z G dd d ej
j Z
G d
d d e
ZG d d
d
e
ZdddZdS )a
Manage shelves of pickled objects.
A "shelf" is a persistent, dictionary-like object. The difference
with dbm databases is that the values (not the keys!) in a shelf can
be essentially arbitrary Python objects -- anything that the "pickle"
module can handle. This includes most class instances, recursive data
types, and objects containing lots of shared sub-objects. The keys
are ordinary strings.
To summarize the interface (key is a string, data is an arbitrary
object):
import shelve
d = shelve.open(filename) # open, with (g)dbm filename -- no suffix
d[key] = data # store data at key (overwrites old data if
# using an existing key)
data = d[key] # retrieve a COPY of the data at key (raise
# KeyError if no such key) -- NOTE that this
# access returns a *copy* of the entry!
del d[key] # delete data stored at key (raises KeyError
# if no such key)
flag = key in d # true if the key exists
list = d.keys() # a list of all existing keys (slow!)
d.close() # close it
Dependent on the implementation, closing a persistent dictionary may
or may not be necessary to flush changes to disk.
Normally, d[key] returns a COPY of the entry. This needs care when
mutable entries are mutated: for example, if d[key] is a list,
d[key].append(anitem)
does NOT modify the entry d[key] itself, as stored in the persistent
mapping -- it only modifies the copy, which is then immediately
discarded, so that the append has NO effect whatsoever. To append an
item to d[key] in a way that will affect the persistent mapping, use:
data = d[key]
data.append(anitem)
d[key] = data
To avoid the problem with mutable entries, you may pass the keyword
argument writeback=True in the call to shelve.open. When you use:
d = shelve.open(filename, writeback=True)
then d keeps a cache of all entries you access, and writes them all back
to the persistent mapping when you call d.close(). This ensures that
such usage as d[key].append(anitem) works as intended.
However, using keyword argument writeback=True may consume vast amount
of memory for the cache, and it may make d.close() very slow, if you
access many of d's entries after opening it in this way: d has no way to
check which of the entries you access are mutable and/or which ones you
actually mutate, so it must cache, and write back at close, all of the
entries that you access. You can call d.sync() to write back all the
entries in the cache, and empty the cache (d.sync() also synchronizes
the persistent dictionary on disk, if feasible).
)DEFAULT_PROTOCOLPickler Unpickler)BytesION)Shelf
BsdDbShelfDbfilenameShelfopenc @ s8 e Zd ZdZdd Ze Z Z Z Z Z Z
dd Z dS ) _ClosedDictz>Marker for a closed dict. Access attempts raise a ValueError.c G s t d)Nz!invalid operation on closed shelf)
ValueError)selfargs r /usr/lib/python3.10/shelve.pyclosedE s z_ClosedDict.closedc C s dS )Nz
r r r r r __repr__I z_ClosedDict.__repr__N) __name__
__module__ __qualname____doc__r __iter____len__ __getitem__ __setitem__ __delitem__keysr r r r r r
B s
r
c @ s e Zd ZdZ d ddZdd Zd d
Zd d Zd d
dZdd Z dd Z
dd Z dd Z dd Z
dd Zdd Zd d ZdS )!r zBase class for shelf implementations.
This is initialized with a dictionary-like object.
See the module's __doc__ string for an overview of the interface.
NFutf-8c C s. || _ |d u r t}|| _|| _i | _|| _d S N)dictr _protocol writebackcache keyencodingr r protocolr" r$ r r r __init__T s
zShelf.__init__c c s$ | j D ] }|| jV qd S r )r r decoder$ )r kr r r r ^ s zShelf.__iter__c C s
t | jS r )lenr r r r r r b s
z
Shelf.__len__c C s | | j| jv S r encoder$ r r keyr r r __contains__e s zShelf.__contains__c C s | | j| jv r
| | S |S r r+ )r r. defaultr r r geth s z Shelf.getc C s^ z| j | }W |S ty. t| j|| j }t| }| jr+|| j |< Y |S Y |S w r ) r# KeyErrorr r r, r$ r loadr" r r. valuefr r r r m s zShelf.__getitem__c C sF | j r|| j|< t }t|| j}|| | | j|| j < d S r )
r" r# r r r! dumpgetvaluer r, r$ )r r. r5 r6 pr r r r w s
zShelf.__setitem__c C s4 | j || j= z| j|= W d S ty Y d S w r )r r, r$ r# r2 r- r r r r s zShelf.__delitem__c C s | S r r r r r r __enter__ r zShelf.__enter__c C s | d S r )close)r typer5 tracebackr r r __exit__ s zShelf.__exit__c C s| | j d u rd S z'| z| j W n ty Y nw W zt | _ W d S d | _ Y d S zt | _ W w d | _ Y w r )r syncr; AttributeErrorr
r r r r r; s$
z Shelf.closec C s t | dsd S | d S )Nr" )hasattrr; r r r r __del__ s
z
Shelf.__del__c C sX | j r | jr d| _ | j D ]\}}|| |< qd| _ i | _t| jdr*| j d S d S )NFTr? )r" r# itemsrA r r? )r r. entryr r r r? s
z
Shelf.syncNFr r )r r r r r' r r r/ r1 r r r r: r> r; rB r? r r r r r M s"
r c @ sF e Zd ZdZ dddZdd Zd d
Zd d Zd
d Zdd Z dS )r a Shelf implementation using the "BSD" db interface.
This adds methods first(), next(), previous(), last() and
set_location() that have no counterpart in [g]dbm databases.
The actual database must be opened using one of the "bsddb"
modules "open" routines (i.e. bsddb.hashopen, bsddb.btopen or
bsddb.rnopen) and passed to the constructor.
See the module's __doc__ string for an overview of the interface.
NFr c C s t | |||| d S r )r r' r% r r r r' s zBsdDbShelf.__init__c C s0 | j |\}}t|}|| jt| fS r )r set_locationr r( r$ r r3 r4 r r r rF s zBsdDbShelf.set_locationc C s. t | j\}}t|}|| jt| fS r )nextr r r( r$ r r3 r4 r r r rG zBsdDbShelf.nextc C . | j \}}t|}|| jt| fS r )r previousr r( r$ r r3 r4 r r r rJ rH zBsdDbShelf.previousc C rI r )r firstr r( r$ r r3 r4 r r r rK rH zBsdDbShelf.firstc C rI r )r lastr r( r$ r r3 r4 r r r rL rH zBsdDbShelf.lastrE )
r r r r r' rF rG rJ rK rL r r r r r s
r c @ s e Zd ZdZdddZdS )r zShelf implementation using the "dbm" generic dbm interface.
This is initialized with the filename for the dbm database.
See the module's __doc__ string for an overview of the interface.
cNFc C s$ dd l }t| ||||| d S )Nr )dbmr r' r )r filenameflagr& r" rN r r r r' s zDbfilenameShelf.__init__rM NF)r r r r r' r r r r r s r rM Fc C s t | |||S )a Open a persistent dictionary for reading and writing.
The filename parameter is the base filename for the underlying
database. As a side-effect, an extension may be added to the
filename and more than one file may be created. The optional flag
parameter has the same interpretation as the flag parameter of
dbm.open(). The optional protocol parameter specifies the
version of the pickle protocol.
See the module's __doc__ string for an overview of the interface.
)r )rO rP r& r" r r r r s
r rQ )r pickler r r ior collections.abc collections__all__abcMutableMappingr
r r r r r r r r s : b+