/snap/core20/2866/usr/lib/python3.8/__pycache__
Edit: /snap/core20/2866/usr/lib/python3.8/__pycache__/copy.cpython-38.pyc (6987B)
U
¼Ê¦iÕ! ã @ sT d Z ddlZddlZddlmZ G dd„ deƒZeZzddlm Z W n e
k
r\ dZ Y nX dddgZ d d„ Z i Z
Zd
d „ Zedƒeeeeeeeeeeeeej ee ƒee ƒej ej fD ] Z!eee!< qºe"ed dƒZ!e!dk räeee!< e#j ee#< e$j ee$< e%j ee%< e&j ee&< e dk r e j ee < [[!dg fd
d„Z'i Z(Zdd„ Z)e)eedƒ< e)eee ƒ< e)eee ƒ< e)ee< e)ee< e)ee< e)ee< e)ee< e)ee< e)eej*< e)ee< e)eej < e)eej < e)eej < e)ee< e'fdd„Z+e+ee#< e'fdd„Z,e,ee< e'fdd„Z-e-ee$< e dk r e-ee < dd„ Z.e.eej/< [dd„ Z0ddde'fdd„Z1[[[ dS ) aÍ Generic (shallow and deep) copying operations.
Interface summary:
import copy
x = copy.copy(y) # make a shallow copy of y
x = copy.deepcopy(y) # make a deep copy of y
For module specific errors, copy.Error is raised.
The difference between shallow and deep copying is only relevant for
compound objects (objects that contain other objects, like lists or
class instances).
- A shallow copy constructs a new compound object and then (to the
extent possible) inserts *the same objects* into it that the
original contains.
- A deep copy constructs a new compound object and then, recursively,
inserts *copies* into it of the objects found in the original.
Two problems often exist with deep copy operations that don't exist
with shallow copy operations:
a) recursive objects (compound objects that, directly or indirectly,
contain a reference to themselves) may cause a recursive loop
b) because deep copy copies *everything* it may copy too much, e.g.
administrative data structures that should be shared even between
copies
Python's deep copy operation avoids these problems by:
a) keeping a table of objects already copied during the current
copying pass
b) letting user-defined classes override the copying operation or the
set of components copied
This version does not copy types like module, class, function, method,
nor stack trace, stack frame, nor file, socket, window, nor array, nor
any similar types.
Classes can use the same interfaces to control copying that they use
to control pickling: they can define methods called __getinitargs__(),
__getstate__() and __setstate__(). See the documentation for module
"pickle" for information on these methods.
é N)Údispatch_tablec @ s e Zd ZdS )ÚErrorN)Ú__name__Ú
__module__Ú __qualname__© r r ú/usr/lib/python3.8/copy.pyr 7 s r )Ú PyStringMapÚcopyÚdeepcopyc C sÈ t | ƒ}t |¡}|r || ƒS t|t ƒr0t| ƒS t|ddƒ}|dk rL|| ƒS t |¡}|dk rh|| ƒ}nBt| ddƒ}|dk r†|dƒ}n$t| ddƒ}|rž|ƒ }n td| ƒ‚t|t ƒr¸| S t
| df|žŽ S )zlShallow copy operation on arbitrary Python objects.
See the module's __doc__ string for more info.
Ú__copy__NÚ
__reduce_ex__é Ú
__reduce__z%un(shallow)copyable object of type %s) ÚtypeÚ_copy_dispatchÚgetÚ
issubclassÚ_copy_immutableÚgetattrr r Ú
isinstanceÚstrÚ _reconstruct)ÚxÚclsÚcopierÚreductorÚrvr r r r
B s,
c C s | S ©Nr )r r r r r k s r ÚCodeTypec C s |dkr i }t | ƒ}| ||¡}||k r,|S t| ƒ}t |¡}|dk rR|| |ƒ}n®t|tƒrht| |ƒ}n˜t| ddƒ}|dk r†||ƒ}nzt |¡}|rž|| ƒ}nBt| ddƒ}|dk r¼|dƒ}n$t| ddƒ}|rÔ|ƒ }n td| ƒ‚t |t
ƒrð| }nt | |f|žŽ }|| k r |||< t | |ƒ |S )ziDeep copy operation on arbitrary Python objects.
See the module's __doc__ string for more info.
NÚ __deepcopy__r
r r z"un(deep)copyable object of type %s)
Úidr r Ú_deepcopy_dispatchr Ú_deepcopy_atomicr r r r r r Ú _keep_alive) r ÚmemoZ_nilÚdÚyr r r r r r r r € sD
ÿ
c C s | S r r ©r r% r r r r# ¶ s r# c C s2 g }||t | ƒ< |j}| D ]}||||ƒƒ q|S r )r! Úappend)r r% r r' r) Úar r r Ú_deepcopy_listÈ s r+ c sh ‡ ‡fdd„| D ƒ}zˆt | ƒ W S tk
r6 Y nX t| |ƒD ] \}}||k rBt|ƒ} qdqB| }|S )Nc s g | ]}ˆ |ˆƒ‘qS r r )Ú.0r* ©r r% r r Ú
Ò s z#_deepcopy_tuple..)r! ÚKeyErrorÚzipÚtuple)r r% r r' ÚkÚjr r- r Ú_deepcopy_tupleÑ s r4 c C s: i }||t | ƒ< | ¡ D ] \}}|||ƒ||||ƒ< q|S r )r! Úitems)r r% r r' ÚkeyÚvaluer r r Ú_deepcopy_dictâ s
r8 c C s t | ƒ| jt| j|ƒƒS r )r Ú__func__r Ú__self__r( r r r Ú_deepcopy_methodì s r; c C s> z|t |ƒ | ¡ W n" tk
r8 | g|t |ƒ< Y nX dS )aM Keeps a reference to the object x in the memo.
Because we remember objects by their id, we have
to assure that possibly temporary objects are kept
alive by referencing them.
We store a reference at the id of the memo, which should
normally not be used unless someone tries to deepcopy
the memo itself...
N)r! r) r/ r( r r r r$ ò s
r$ c sb ˆd k }|r$|r$‡ ‡fdd„|D ƒ}||Ž } |r<| ˆt | ƒ< |d k rÆ|rRˆ |ˆƒ}t| dƒrh| |¡ n^t|tƒrˆt|ƒdkrˆ|\}}
nd }
|d k r | j |¡ |
d k rÆ|
¡ D ]\} } t | | | ƒ q°|d k r|rô|D ]}
ˆ |
ˆƒ}
|
|
¡ qØn|D ]}
|
|
¡ qø|d k r^|rF|D ]&\} } ˆ | ˆƒ} ˆ | ˆƒ} | | | < q n|D ]\} } | | | < qJ| S )Nc 3 s | ]}ˆ |ˆƒV qd S r r )r, Úargr- r r Ú s z _reconstruct..Ú __setstate__é ) r! Úhasattrr> r r1 ÚlenÚ__dict__Úupdater5 Úsetattrr) )r r% ÚfuncÚargsÚstateZlistiterZdictiterr Zdeepr' Z slotstater6 r7 Úitemr r- r r sF
r )2Ú__doc__ÚtypesÚweakrefÚcopyregr Ú Exceptionr ÚerrorZorg.python.corer Ú ImportErrorÚ__all__r
r r& r r ÚintÚfloatÚboolÚcomplexr r1 ÚbytesÚ frozensetÚrangeÚsliceÚpropertyÚBuiltinFunctionTypeÚEllipsisÚNotImplementedÚ FunctionTypeÚrefÚtr ÚlistÚdictÚsetÚ bytearrayr r" r# r r+ r4 r8 r; Ú
MethodTyper$ r r r r r Ú s’ 2
' ý
4
þ
-