o ?Ogp!@sdZddlmZmZmZddlmZddlZgdZ Gdddej j Z Gdd d ej j Z Gd d d e ZGd 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@s8eZdZdZddZeZZZZZ Z ddZ dS) _ClosedDictz>Marker for a closed dict. Access attempts raise a ValueError.cGstd)Nz!invalid operation on closed shelf) ValueError)selfargsr-/opt/alt/python310/lib64/python3.10/shelve.pyclosedEsz_ClosedDict.closedcCsdS)Nzrr rrr__repr__Iz_ClosedDict.__repr__N) __name__ __module__ __qualname____doc__r__iter____len__ __getitem__ __setitem__ __delitem__keysrrrrrr Bs  r c@seZdZdZ  dddZddZd d Zd d Zd d dZddZ ddZ ddZ ddZ ddZ ddZddZddZdS)!rzBase 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-8cCs.||_|dur t}||_||_i|_||_dSN)dictr _protocol writebackcache keyencodingr r protocolr"r$rrr__init__Ts zShelf.__init__ccs$|jD] }||jVqdSr)r rdecoder$)r krrrr^szShelf.__iter__cCs t|jSr)lenr rrrrrbs z Shelf.__len__cCs||j|jvSrencoder$r r keyrrr __contains__eszShelf.__contains__cCs||j|jvr ||S|Srr+)r r.defaultrrrgethsz Shelf.getcCs^z|j|}W|Sty.t|j||j}t|}|jr+||j|<Y|SY|Swr) r#KeyErrorrr r,r$rloadr"r r.valuefrrrrms    zShelf.__getitem__cCsF|jr||j|<t}t||j}||||j||j <dSr) r"r#rrr!dumpgetvaluer r,r$)r r.r5r6prrrrws    zShelf.__setitem__cCs4|j||j=z|j|=WdStyYdSwr)r r,r$r#r2r-rrrrs  zShelf.__delitem__cCs|Srrrrrr __enter__rzShelf.__enter__cCs |dSr)close)r typer5 tracebackrrr__exit__s zShelf.__exit__c Cs||jdurdSz'|z|jWn tyYnwWzt|_WdSd|_YdSzt|_Wwd|_Ywr)r syncr;AttributeErrorr rrrrr;s$     z Shelf.closecCst|dsdS|dS)Nr")hasattrr;rrrr__del__s  z Shelf.__del__cCsX|jr|jrd|_|jD]\}}|||<qd|_i|_t|jdr*|jdSdS)NFTr?)r"r#itemsrAr r?)r r.entryrrrr?s   z Shelf.syncNFrr)rrrrr'rrr/r1rrrr:r>r;rBr?rrrrrMs"     rc@sFeZdZdZ  dddZddZd d Zd d Zd dZddZ dS)raShelf 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%rrrr'szBsdDbShelf.__init__cCs0|j|\}}t|}||jt|fSr)r set_locationrr(r$rr3r4rrrrFszBsdDbShelf.set_locationcCs.t|j\}}t|}||jt|fSr)nextr rr(r$rr3r4rrrrGzBsdDbShelf.nextcC.|j\}}t|}||jt|fSr)r previousrr(r$rr3r4rrrrJrHzBsdDbShelf.previouscCrIr)r firstrr(r$rr3r4rrrrKrHzBsdDbShelf.firstcCrIr)r lastrr(r$rr3r4rrrrLrHzBsdDbShelf.lastrE) rrrrr'rFrGrJrKrLrrrrrs   rc@seZdZdZdddZdS)rzShelf 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$ddl}t||||||dS)Nr)dbmrr'r )r filenameflagr&r"rNrrrr'szDbfilenameShelf.__init__rMNF)rrrrr'rrrrrsrrMFcCst||||S)aOpen 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)rOrPr&r"rrrr s r rQ)rpicklerrriorZcollections.abc collections__all__abcMutableMappingr rrrr rrrrs:  b+