404 Not Found

Sh3ll
Server : LiteSpeed
System : Linux premium84.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
User : claqxcrl ( 523)
PHP Version : 8.1.32
Disable Function : NONE
Directory : /lib64/python3.8/__pycache__/
Upload File :
Current File : //lib64/python3.8/__pycache__/copy.cpython-38.pyc
U

e5d�!�@sTdZddlZddlZddlmZGdd�de�ZeZzddlm	Z	Wne
k
r\dZ	YnXdddgZd	d�ZiZ
Zd
d�Zed�eeeeeeeeeeeeejee�ee�ejej fD]Z!eee!<q�e"edd�Z!e!dk	r�eee!<e#jee#<e$jee$<e%jee%<e&jee&<e	dk	�r e	jee	<[[!dgfd
d�Z'iZ(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	�re-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@seZdZdS)�ErrorN)�__name__�
__module__�__qualname__�rr�/usr/lib64/python3.8/copy.pyr7sr)�PyStringMap�copy�deepcopycCs�t|�}t�|�}|r||�St|t�r0t|�St|dd�}|dk	rL||�St�|�}|dk	rh||�}nBt|dd�}|dk	r�|d�}n$t|dd�}|r�|�}ntd|��t|t	�r�|St
|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�getattrrr�
isinstance�str�_reconstruct)�x�cls�copier�reductor�rvrrrr
Bs,





cCs|S�Nr)rrrrrksr�CodeTypec	Cs |dkri}t|�}|�||�}||k	r,|St|�}t�|�}|dk	rR|||�}n�t|t�rht||�}n�t|dd�}|dk	r�||�}nzt�|�}|r�||�}nBt|dd�}|dk	r�|d�}n$t|dd�}|r�|�}ntd|��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
rrz"un(deep)copyable object of type %s)
�idrr�_deepcopy_dispatchr�_deepcopy_atomicrrrrrr�_keep_alive)	r�memoZ_nil�d�yrrrrrrrr�sD





�


cCs|Srr�rr%rrrr#�sr#cCs2g}||t|�<|j}|D]}||||��q|Sr)r!�append)rr%rr'r)�arrr�_deepcopy_list�sr+csh��fdd�|D�}z�t|�WStk
r6YnXt||�D]\}}||k	rBt|�}qdqB|}|S)Ncsg|]}�|���qSrr)�.0r*�rr%rr�
<listcomp>�sz#_deepcopy_tuple.<locals>.<listcomp>)r!�KeyError�zip�tuple)rr%rr'�k�jrr-r�_deepcopy_tuple�sr4cCs:i}||t|�<|��D]\}}|||�||||�<q|Sr)r!�items)rr%rr'�key�valuerrr�_deepcopy_dict�s
r8cCst|�|jt|j|��Sr)r�__func__r�__self__r(rrr�_deepcopy_method�sr;cCs>z|t|��|�Wn"tk
r8|g|t|�<YnXdS)aMKeeps 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(rrrr$�s
r$csb�dk	}|r$|r$��fdd�|D�}||�}	|r<|	�t|�<|dk	r�|rR�|��}t|	d�rh|	�|�n^t|t�r�t|�dkr�|\}}
nd}
|dk	r�|	j�|�|
dk	r�|
��D]\}}t	|	||�q�|dk	�r|r�|D]}
�|
��}
|	�
|
�q�n|D]}
|	�
|
�q�|dk	�r^|�rF|D]&\}}�|��}�|��}||	|<�qn|D]\}}||	|<�qJ|	S)Nc3s|]}�|��VqdSrr)r,�argr-rr�	<genexpr>sz_reconstruct.<locals>.<genexpr>�__setstate__�)r!�hasattrr>rr1�len�__dict__�updater5�setattrr))rr%�func�args�stateZlistiterZdictiterrZdeepr'Z	slotstater6r7�itemrr-rrsF







r)2�__doc__�types�weakref�copyregr�	Exceptionr�errorZorg.python.corer	�ImportError�__all__r
rr&rr�int�float�bool�complexrr1�bytes�	frozenset�range�slice�property�BuiltinFunctionType�Ellipsis�NotImplemented�FunctionType�ref�tr�list�dict�set�	bytearrayrr"r#rr+r4r8r;�
MethodTyper$rrrrr�<module>s�2

'�






4





�
-
ZeroDay Forums Mini