| Dir : /lib64/python3.8/__pycache__/ |
| Server: Linux apophis.o2switch.net 4.18.0-553.111.1.lve.el8.x86_64 #1 SMP Fri Mar 13 13:42:17 UTC 2026 x86_64 IP: 109.234.164.184 |
| Dir : //lib64/python3.8/__pycache__/copy.cpython-38.pyc |
U
e5d�! � @ 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/lib64/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 �
<listcomp>� s z#_deepcopy_tuple.<locals>.<listcomp>)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 � <genexpr> s z _reconstruct.<locals>.<genexpr>� __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 �<module> s� 2
' �
4
�
-