Operation   : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64
Software     : Apache
Server IP    : 162.0.232.56 | Your IP: 216.73.216.111
Domains      : 1034 Domain(s)
Permission   : [ 0755 ]

U

i�fO!�@s�dZd
dl
mZmZ
d
dlmZ
d
dlZddddgZGd	d
�d
ej	j
�ZGdd�dej	j
�ZGdd�de�Z
Gd
d�de�Zddd�
ZdS)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).
�)�Pickler�	Unpickler)
�BytesION�Shelf�
BsdDbShelf�DbfilenameShelf�openc@s8eZ
dZd
Zdd�ZeZZZZZ	Z
dd�ZdS)�_ClosedDictz>Marker for a closed dict.  Access attempts raise a ValueError.c
Gstd
�
�
dS)Nz!invalid operation on closed shelf)
�
ValueError)�self�args�r
�+/opt/alt/python38/lib64/python3.8/shelve.py�closedEs
z_ClosedDict.closedc


Csd
S)Nz<Closed Dictionary>r
�
rr
r
r�__repr__Is
z_ClosedDict.__repr__N)�__name__�
__module__�__qualname__�__doc__r�__iter__�__len__�__getitem__�__setitem__�__delitem__�keysrr
r
r
rr	Bs
r	c@s|eZ
dZd
Zddd�
Zdd�Zd	d
�Zdd�Zd d
d�
Zdd�Z	dd�Z
dd�Zdd�Zdd�Z
dd�Zdd�Zdd�ZdS)!rz�Base class for shelf implementations.

    This is initialized with a dictionary-like object.
    See the module's __doc__ string for an overview of the interface.
    NF�utf-8cCs.|
|_|dkrd
}||_
||_i|_||_dS)N�)�dict�	_protocol�	writeback�cache�keyencoding�rr�protocolr r"r
r
r�__init__Ts





zShelf.__init__c
cs"|j�
�D]}
|
�|j�
V
q
dS�
N)rr�decoder")r�
kr
r
rr^s

zShelf.__iter__c

Cs
t|j
�
Sr&)�lenrrr
r
rrbs
z
Shelf.__len__cCs|
�|j
�
|jkSr&��encoder"r�r�keyr
r
r�__contains__es
zShelf.__contains__cCs|
�|j
�
|jkr||
S|Sr&r*)rr-�defaultr
r
r�geths


z	Shelf.getcCsZz|j|
}WnFt
k
rT


t|j|
�|j�
�
}t|�
��}|jrP||j|
<YnX|Sr&)	r!�KeyErrorrrr+r"r�loadr �rr-�value�
fr
r
rrms







zShelf.__getitem__cCsF|jr||j
|
<t�}t||j�}|�|�

|��|j|
�|j	�
<dSr&)
r r!rrr�dump�getvaluerr+r")rr-r4r5�
pr
r
rrws







zShelf.__setitem__cCs6|j|
�
|j�
=z|j|
=Wntk
r0


YnXdSr&)rr+r"r!r1r,r
r
rrs





zShelf.__delitem__c


Cs|Sr&r
rr
r
r�	__enter__�s
zShelf.__enter__cCs|��
dSr&)
�close)r�typer4�	tracebackr
r
r�__exit__�s
zShelf.__exit__c

Csf|jdkrdSz0|��
z|j��
Wntk
r:


YnXW5zt
�|_Wn


d|_YnXXdSr&)rr	�syncr:�AttributeErrorrr
r
rr:�s












zShelf.closec

Cst|d
�sdS|�
�
dS)Nr )�hasattrr:rr
r
r�__del__�s


z
Shelf.__del__c
CsT|jr:|j
r:d
|_|j
��D]\}
}|||
<qd|_i|_
t|jd�rP|j��
dS)NFTr>)r r!�itemsr@rr>)rr-�entryr
r
rr>�s








z
Shelf.sync)NFr)
N)rrrrr%rrr.r0rrrr9r=r:rAr>r
r
r
rrMs 

�



c@sBeZ
dZd
Zddd�
Zdd�Zd	d
�Zdd�Zd
d�Zdd�Z	dS)ra�
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.
    NFrcCst�
||
|||�
dSr&)rr%r#r
r
rr%�szBsdDbShelf.__init__cCs0|j�
|
�
\}
}t|�
}|
�|j�
t|�
��fSr&)r�set_locationrr'r"rr2r3r
r
rrD�s


zBsdDbShelf.set_locationc
Cs.t|j
�
\}
}t|�
}|
�|j�
t|�
��fSr&)�nextrrr'r"rr2r3r
r
rrE�s


zBsdDbShelf.nextc
Cs.|j�
�\}
}t|�
}|
�|j�
t|�
��fSr&)r�previousrr'r"rr2r3r
r
rrF�s


zBsdDbShelf.previousc
Cs.|j�
�\}
}t|�
}|
�|j�
t|�
��fSr&)r�firstrr'r"rr2r3r
r
rrG�s


zBsdDbShelf.firstc
Cs.|j�
�\}
}t|�
}|
�|j�
t|�
��fSr&)r�lastrr'r"rr2r3r
r
rrH�s


zBsdDbShelf.last)NFr)
rrrrr%rDrErFrGrHr
r
r
rr�s

�
c@seZ
dZd
Zddd�
ZdS)rz�Shelf 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.
    �
cNFcCs$d
dl}t
�||�|
|�||�
dS)Nr
)�dbmrr%r)r�filename�flagr$r rJr
r
rr%�s

zDbfilenameShelf.__init__)rINF)rrrrr%r
r
r
rr�s
rIFcCst||
||�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)rKrLr$r r
r
rr�s
)rINF)r�picklerr�iorZcollections.abc�collections�__all__�abc�MutableMappingr	rrrrr
r
r
r�<module>
s:
b+