?????????? ????????? - ??????????????? - /home/agenciai/.local/lib/python3.9/site-packages/sqlalchemy/engine/__pycache__/create.cpython-39.pyc
???????
a ��Jh�� � & @ s� d dl mZ d dlZd dlZd dlmZ d dlmZ d dlmZ d dlmZ d dlmZ d dlm Z d d lm Z d d lm Z d d lm Z d d l mZ d dl mZ d dlmZ d dlmZ ddl mZ ddl mZ ddl mZ ddlmZ ddlmZ ddlm Z ddlm Z ej �r�d dlm Z d dlm Z d dlm!Z! d d lm"Z" d d lm#Z# dd l$m%Z% dd lm&Z& dd lm'Z' dd!lm(Z( dd"lm)Z) dd#l*m+Z+ e d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d$d%� d&d'd(d)d*d*d(d+d,d(d,d-d.d/d/d0d1d0d-d2d3d4d5d1d(d-d-d6d7d(d8d-d(d9d:d;�#d<d=��Z,e d&d9d:d>�d?d=��Z,ej-d@dAdBdC�dDd9d:d>�dEd=��Z,d[dGd1d9d:dH�dIdJ�Z.e d$d$d$d$d$d$d$d$dK�d&d5d1d(d-d-d6d7d(d9dLdM� dNdO��Z/e d&d9dLd>�dPdO��Z/d&d9dLd>�dQdO�Z/e dRdSdTdUdVdWdXdYdZ��Z0dS )\� )� annotationsN)�Any)�Callable)�cast)�Dict)�List)�Optional)�overload)�Type)�Union� )�base)�url)�DBAPIConnection)�create_mock_engine� )�event)�exc)�util)�_AdhocProxiedConnection)�ConnectionPoolEntry)�compiler)� immutabledict)�Engine)�_ExecuteOptions)� _ParamStyle)�IsolationLevel)�URL)� _EchoFlagType)�_CreatorFnType)�_CreatorWRecFnType)�_ResetStyleArgType)�Pool)�Literal.) � connect_args�convert_unicode�creator�echo� echo_pool�enable_from_linting�execution_options�hide_parameters�implicit_returning�insertmanyvalues_page_size�isolation_level�json_deserializer�json_serializer� label_length� logging_name�max_identifier_length� max_overflow�module� paramstyle�pool� poolclass�pool_logging_name� pool_pre_ping� pool_size� pool_recycle�pool_reset_on_return� pool_timeout� pool_use_lifo�plugins�query_cache_size�use_insertmanyvalueszUnion[str, URL]zDict[Any, Any]�boolz)Union[_CreatorFnType, _CreatorWRecFnType]r r z Literal[True]�intr zCallable[..., Any]z Optional[int]�str� Optional[Any]zOptional[_ParamStyle]zOptional[Pool]zOptional[Type[Pool]]z Optional[_ResetStyleArgType]�floatz List[str]r r )#r r$ r% r& r' r( r) r* �futurer+ r, r- r. r/ r0 r1 r2 r3 r4 r5 r6 r7 r8 r9 r: r; r< r= r> r? r@ rA rB �kwargs�returnc " K s d S �N� )"r r$ r% r& r' r( r) r* rH r+ r, r- r. r/ r0 r1 r2 r3 r4 r5 r6 r7 r8 r9 r: r; r< r= r> r? r@ rA rB rI rL rL �M/home/agenciai/.local/lib/python3.9/site-packages/sqlalchemy/engine/create.py� create_engine0 s %rN )r rI rJ c K s d S rK rL �r rI rL rL rM rN X s )�1.4a" The :paramref:`_sa.create_engine.strategy` keyword is deprecated, and the only argument accepted is 'mock'; please use :func:`.create_mock_engine` going forward. For general customization of create_engine which may have been accomplished using strategies, see :class:`.CreateEnginePlugin`.)rP a The :paramref:`_sa.create_engine.empty_in_strategy` keyword is deprecated, and no longer has any effect. All IN expressions are now rendered using the "expanding parameter" strategy which renders a set of boundexpressions, or an "empty set" SELECT, at statement executiontime.)�2.0zvThe :paramref:`_sa.create_engine.implicit_returning` parameter is deprecated and will be removed in a future release. )�strategy�empty_in_strategyr, zUnion[str, _url.URL]c s� d�v r8�� d�}|dkr*t| fi ���S t�d| ���� dd� t�| �}|���\}}�|�� }�� dd�}|r�|�|��n |� |���� dd�r�d<d d d d ���fd d� }n�j }i }t � ��D ]} | �v r�|| �|| < qȈ� dd�} | du �r�i } d�j v �r�j } n<t�d��rFt��j��rFt �d�� d�d� �j} n�j } t �| �D ] } | �v �rV|| �| | < �qV| f i | ��} | |d< |�dtj� �� dd�} | �r�|d tjN < |D ]}|��|� �q��f i |�����|�\}���|di �� d�v �r&t ��d ��r&t �dd� t |�� |dd�}|du �r�d=d d d �� ��fd d � }|d!|�}|d"d�}|du �r��� |�}d#�i}t � |�D ](} t � | | �}|�v �r�||�|| < �q�|D ]}|� ||� �q�||fi |��}n�|_!t|d$��r6|j"�j#u�r6tjd%|j$j%� d&�j#�s&d'nd(� d)�d*d+��|d,d��sLt�d-��t&j'}i }t � |�D ] } | �v �r`|| �|| < �q`�� d.d�}��r�t(d/d0�)d1d2� �D ���j$j%|j$j%|j%f ��||�|fi |���|�rR��*|����r d d3d4d5��fd6d7� }t+�,|d8|� ��-� }|�r(t+�,|d8|� d d3d4d5���fd9d:� }t+j,|d8|dd;� ��.�� |�u�rp|�.�� |D ]}|�.�� �qt�S )>a�E Create a new :class:`_engine.Engine` instance. The standard calling form is to send the :ref:`URL <database_urls>` as the first positional argument, usually a string that indicates database dialect and connection arguments:: engine = create_engine("postgresql+psycopg2://scott:tiger@localhost/test") .. note:: Please review :ref:`database_urls` for general guidelines in composing URL strings. In particular, special characters, such as those often part of passwords, must be URL encoded to be properly parsed. Additional keyword arguments may then follow it which establish various options on the resulting :class:`_engine.Engine` and its underlying :class:`.Dialect` and :class:`_pool.Pool` constructs:: engine = create_engine( "mysql+mysqldb://scott:tiger@hostname/dbname", pool_recycle=3600, echo=True, ) The string form of the URL is ``dialect[+driver]://user:password@host/dbname[?key=value..]``, where ``dialect`` is a database name such as ``mysql``, ``oracle``, ``postgresql``, etc., and ``driver`` the name of a DBAPI, such as ``psycopg2``, ``pyodbc``, ``cx_oracle``, etc. Alternatively, the URL can be an instance of :class:`~sqlalchemy.engine.url.URL`. ``**kwargs`` takes a wide variety of options which are routed towards their appropriate components. Arguments may be specific to the :class:`_engine.Engine`, the underlying :class:`.Dialect`, as well as the :class:`_pool.Pool`. Specific dialects also accept keyword arguments that are unique to that dialect. Here, we describe the parameters that are common to most :func:`_sa.create_engine()` usage. Once established, the newly resulting :class:`_engine.Engine` will request a connection from the underlying :class:`_pool.Pool` once :meth:`_engine.Engine.connect` is called, or a method which depends on it such as :meth:`_engine.Engine.execute` is invoked. The :class:`_pool.Pool` in turn will establish the first actual DBAPI connection when this request is received. The :func:`_sa.create_engine` call itself does **not** establish any actual DBAPI connections directly. .. seealso:: :doc:`/core/engines` :doc:`/dialects/index` :ref:`connections_toplevel` :param connect_args: a dictionary of options which will be passed directly to the DBAPI's ``connect()`` method as additional keyword arguments. See the example at :ref:`custom_dbapi_args`. :param creator: a callable which returns a DBAPI connection. This creation function will be passed to the underlying connection pool and will be used to create all new database connections. Usage of this function causes connection parameters specified in the URL argument to be bypassed. This hook is not as flexible as the newer :meth:`_events.DialectEvents.do_connect` hook which allows complete control over how a connection is made to the database, given the full set of URL arguments and state beforehand. .. seealso:: :meth:`_events.DialectEvents.do_connect` - event hook that allows full control over DBAPI connection mechanics. :ref:`custom_dbapi_args` :param echo=False: if True, the Engine will log all statements as well as a ``repr()`` of their parameter lists to the default log handler, which defaults to ``sys.stdout`` for output. If set to the string ``"debug"``, result rows will be printed to the standard output as well. The ``echo`` attribute of ``Engine`` can be modified at any time to turn logging on and off; direct control of logging is also available using the standard Python ``logging`` module. .. seealso:: :ref:`dbengine_logging` - further detail on how to configure logging. :param echo_pool=False: if True, the connection pool will log informational output such as when connections are invalidated as well as when connections are recycled to the default log handler, which defaults to ``sys.stdout`` for output. If set to the string ``"debug"``, the logging will include pool checkouts and checkins. Direct control of logging is also available using the standard Python ``logging`` module. .. seealso:: :ref:`dbengine_logging` - further detail on how to configure logging. :param empty_in_strategy: No longer used; SQLAlchemy now uses "empty set" behavior for IN in all cases. :param enable_from_linting: defaults to True. Will emit a warning if a given SELECT statement is found to have un-linked FROM elements which would cause a cartesian product. .. versionadded:: 1.4 .. seealso:: :ref:`change_4737` :param execution_options: Dictionary execution options which will be applied to all connections. See :meth:`~sqlalchemy.engine.Connection.execution_options` :param future: Use the 2.0 style :class:`_engine.Engine` and :class:`_engine.Connection` API. As of SQLAlchemy 2.0, this parameter is present for backwards compatibility only and must remain at its default value of ``True``. The :paramref:`_sa.create_engine.future` parameter will be deprecated in a subsequent 2.x release and eventually removed. .. versionadded:: 1.4 .. versionchanged:: 2.0 All :class:`_engine.Engine` objects are "future" style engines and there is no longer a ``future=False`` mode of operation. .. seealso:: :ref:`migration_20_toplevel` :param hide_parameters: Boolean, when set to True, SQL statement parameters will not be displayed in INFO logging nor will they be formatted into the string representation of :class:`.StatementError` objects. .. versionadded:: 1.3.8 .. seealso:: :ref:`dbengine_logging` - further detail on how to configure logging. :param implicit_returning=True: Legacy parameter that may only be set to True. In SQLAlchemy 2.0, this parameter does nothing. In order to disable "implicit returning" for statements invoked by the ORM, configure this on a per-table basis using the :paramref:`.Table.implicit_returning` parameter. :param insertmanyvalues_page_size: number of rows to format into an INSERT statement when the statement uses "insertmanyvalues" mode, which is a paged form of bulk insert that is used for many backends when using :term:`executemany` execution typically in conjunction with RETURNING. Defaults to 1000, but may also be subject to dialect-specific limiting factors which may override this value on a per-statement basis. .. versionadded:: 2.0 .. seealso:: :ref:`engine_insertmanyvalues` :ref:`engine_insertmanyvalues_page_size` :paramref:`_engine.Connection.execution_options.insertmanyvalues_page_size` :param isolation_level: optional string name of an isolation level which will be set on all new connections unconditionally. Isolation levels are typically some subset of the string names ``"SERIALIZABLE"``, ``"REPEATABLE READ"``, ``"READ COMMITTED"``, ``"READ UNCOMMITTED"`` and ``"AUTOCOMMIT"`` based on backend. The :paramref:`_sa.create_engine.isolation_level` parameter is in contrast to the :paramref:`.Connection.execution_options.isolation_level` execution option, which may be set on an individual :class:`.Connection`, as well as the same parameter passed to :meth:`.Engine.execution_options`, where it may be used to create multiple engines with different isolation levels that share a common connection pool and dialect. .. versionchanged:: 2.0 The :paramref:`_sa.create_engine.isolation_level` parameter has been generalized to work on all dialects which support the concept of isolation level, and is provided as a more succinct, up front configuration switch in contrast to the execution option which is more of an ad-hoc programmatic option. .. seealso:: :ref:`dbapi_autocommit` :param json_deserializer: for dialects that support the :class:`_types.JSON` datatype, this is a Python callable that will convert a JSON string to a Python object. By default, the Python ``json.loads`` function is used. .. versionchanged:: 1.3.7 The SQLite dialect renamed this from ``_json_deserializer``. :param json_serializer: for dialects that support the :class:`_types.JSON` datatype, this is a Python callable that will render a given object as JSON. By default, the Python ``json.dumps`` function is used. .. versionchanged:: 1.3.7 The SQLite dialect renamed this from ``_json_serializer``. :param label_length=None: optional integer value which limits the size of dynamically generated column labels to that many characters. If less than 6, labels are generated as "_(counter)". If ``None``, the value of ``dialect.max_identifier_length``, which may be affected via the :paramref:`_sa.create_engine.max_identifier_length` parameter, is used instead. The value of :paramref:`_sa.create_engine.label_length` may not be larger than that of :paramref:`_sa.create_engine.max_identfier_length`. .. seealso:: :paramref:`_sa.create_engine.max_identifier_length` :param logging_name: String identifier which will be used within the "name" field of logging records generated within the "sqlalchemy.engine" logger. Defaults to a hexstring of the object's id. .. seealso:: :ref:`dbengine_logging` - further detail on how to configure logging. :paramref:`_engine.Connection.execution_options.logging_token` :param max_identifier_length: integer; override the max_identifier_length determined by the dialect. if ``None`` or zero, has no effect. This is the database's configured maximum number of characters that may be used in a SQL identifier such as a table name, column name, or label name. All dialects determine this value automatically, however in the case of a new database version for which this value has changed but SQLAlchemy's dialect has not been adjusted, the value may be passed here. .. versionadded:: 1.3.9 .. seealso:: :paramref:`_sa.create_engine.label_length` :param max_overflow=10: the number of connections to allow in connection pool "overflow", that is connections that can be opened above and beyond the pool_size setting, which defaults to five. this is only used with :class:`~sqlalchemy.pool.QueuePool`. :param module=None: reference to a Python module object (the module itself, not its string name). Specifies an alternate DBAPI module to be used by the engine's dialect. Each sub-dialect references a specific DBAPI which will be imported before first connect. This parameter causes the import to be bypassed, and the given module to be used instead. Can be used for testing of DBAPIs as well as to inject "mock" DBAPI implementations into the :class:`_engine.Engine`. :param paramstyle=None: The `paramstyle <https://legacy.python.org/dev/peps/pep-0249/#paramstyle>`_ to use when rendering bound parameters. This style defaults to the one recommended by the DBAPI itself, which is retrieved from the ``.paramstyle`` attribute of the DBAPI. However, most DBAPIs accept more than one paramstyle, and in particular it may be desirable to change a "named" paramstyle into a "positional" one, or vice versa. When this attribute is passed, it should be one of the values ``"qmark"``, ``"numeric"``, ``"named"``, ``"format"`` or ``"pyformat"``, and should correspond to a parameter style known to be supported by the DBAPI in use. :param pool=None: an already-constructed instance of :class:`~sqlalchemy.pool.Pool`, such as a :class:`~sqlalchemy.pool.QueuePool` instance. If non-None, this pool will be used directly as the underlying connection pool for the engine, bypassing whatever connection parameters are present in the URL argument. For information on constructing connection pools manually, see :ref:`pooling_toplevel`. :param poolclass=None: a :class:`~sqlalchemy.pool.Pool` subclass, which will be used to create a connection pool instance using the connection parameters given in the URL. Note this differs from ``pool`` in that you don't actually instantiate the pool in this case, you just indicate what type of pool to be used. :param pool_logging_name: String identifier which will be used within the "name" field of logging records generated within the "sqlalchemy.pool" logger. Defaults to a hexstring of the object's id. .. seealso:: :ref:`dbengine_logging` - further detail on how to configure logging. :param pool_pre_ping: boolean, if True will enable the connection pool "pre-ping" feature that tests connections for liveness upon each checkout. .. versionadded:: 1.2 .. seealso:: :ref:`pool_disconnects_pessimistic` :param pool_size=5: the number of connections to keep open inside the connection pool. This used with :class:`~sqlalchemy.pool.QueuePool` as well as :class:`~sqlalchemy.pool.SingletonThreadPool`. With :class:`~sqlalchemy.pool.QueuePool`, a ``pool_size`` setting of 0 indicates no limit; to disable pooling, set ``poolclass`` to :class:`~sqlalchemy.pool.NullPool` instead. :param pool_recycle=-1: this setting causes the pool to recycle connections after the given number of seconds has passed. It defaults to -1, or no timeout. For example, setting to 3600 means connections will be recycled after one hour. Note that MySQL in particular will disconnect automatically if no activity is detected on a connection for eight hours (although this is configurable with the MySQLDB connection itself and the server configuration as well). .. seealso:: :ref:`pool_setting_recycle` :param pool_reset_on_return='rollback': set the :paramref:`_pool.Pool.reset_on_return` parameter of the underlying :class:`_pool.Pool` object, which can be set to the values ``"rollback"``, ``"commit"``, or ``None``. .. seealso:: :ref:`pool_reset_on_return` :param pool_timeout=30: number of seconds to wait before giving up on getting a connection from the pool. This is only used with :class:`~sqlalchemy.pool.QueuePool`. This can be a float but is subject to the limitations of Python time functions which may not be reliable in the tens of milliseconds. .. note: don't use 30.0 above, it seems to break with the :param tag :param pool_use_lifo=False: use LIFO (last-in-first-out) when retrieving connections from :class:`.QueuePool` instead of FIFO (first-in-first-out). Using LIFO, a server-side timeout scheme can reduce the number of connections used during non- peak periods of use. When planning for server-side timeouts, ensure that a recycle or pre-ping strategy is in use to gracefully handle stale connections. .. versionadded:: 1.3 .. seealso:: :ref:`pool_use_lifo` :ref:`pool_disconnects` :param plugins: string list of plugin names to load. See :class:`.CreateEnginePlugin` for background. .. versionadded:: 1.2.3 :param query_cache_size: size of the cache used to cache the SQL string form of queries. Set to zero to disable caching. The cache is pruned of its least recently used items when its size reaches N * 1.5. Defaults to 500, meaning the cache will always store at least 500 SQL statements when filled, and will grow up to 750 items at which point it is pruned back down to 500 by removing the 250 least recently used items. Caching is accomplished on a per-statement basis by generating a cache key that represents the statement's structure, then generating string SQL for the current dialect only if that key is not present in the cache. All statements support caching, however some features such as an INSERT with a large set of parameters will intentionally bypass the cache. SQL logging will indicate statistics for each statement whether or not it were pull from the cache. .. note:: some ORM functions related to unit-of-work persistence as well as some attribute loading strategies will make use of individual per-mapper caches outside of the main cache. .. seealso:: :ref:`sql_caching` .. versionadded:: 1.4 :param use_insertmanyvalues: True by default, use the "insertmanyvalues" execution style for INSERT..RETURNING statements by default. .. versionadded:: 2.0 .. seealso:: :ref:`engine_insertmanyvalues` rR �mockzunknown strategy: %rrS N� _is_asyncF�_coerce_configrE rF r )�key�defaultrJ c s( �� | |�}| � jv r$� j| |�}|S rK )�popZengine_config_types)rW rX �value)� dialect_clsrI rL rM � pop_kwarg2 s z create_engine.<locals>.pop_kwargr5 � import_dbapi�dbapiz�The dbapi() classmethod on dialect classes has been renamed to import_dbapi(). Implement an import_dbapi() classmethod directly on class zd to remove this warning; the old .dbapi() classmethod may be maintained for backwards compatibility.rQ Zcompiler_lintingr) Tr$ Zasync_fallbackzXThe async_fallback dialect argument is deprecated and will be removed in SQLAlchemy 2.1.r7 z Optional[ConnectionPoolEntry]r )�connection_recordrJ c sH �j r8�jjD ](}tt|�| � ���}|d ur| S q�j� i ���S rK )� _has_events�dispatchZ do_connectr r �connect)r_ �fn� connection)�cargs�cparams�dialectrL rM rb z s � z create_engine.<locals>.connectr& r8 rg � _is_asyncioz Pool class z cannot be used with znon-� zasyncio engineZpcls)�coderH zIThe 'future' parameter passed to create_engine() may only be set to True.� _initializez�Invalid argument(s) %s sent to create_engine(), using configuration %s/%s/%s. Please check that the keyword arguments are appropriate for this combination of components.�,c s s | ]}d | V qdS )z'%s'NrL )�.0�krL rL rM � <genexpr>� � z create_engine.<locals>.<genexpr>r �None)�dbapi_connectionr_ rJ c s � d us J �� | � d S rK rL )rr r_ )� do_on_connectrL rM � on_connect� s z!create_engine.<locals>.on_connectrb c sh t j�t| |�dddd�}tj|_z&� �|� W |jsd|jsd� � |j � n|jsb|jsb� � |j � 0 d S )NF)rd r` Z_allow_revalidateZ_allow_autobegin) r � Connectionr r � EMPTY_DICTZ_execution_optionsZ initializeZ invalidated�closedZ do_rollbackrd )rr r_ �c)rg �enginerL rM � first_connect� s �� � z$create_engine.<locals>.first_connect)Z_once_unless_exception)N)N)/rY r r � ArgumentError�_urlZmake_urlZ_instantiate_pluginsZ_get_entrypointZget_async_dialect_clsZget_dialect_clsr Zget_cls_kwargs�__dict__r] �hasattr�inspect�ismethodr^ Zwarn_deprecatedZget_func_kwargs� setdefaultr Z NO_LINTINGZCOLLECT_CARTESIAN_PRODUCTSZhandle_dialect_kwargsZcreate_connect_args�updateZasbool�listZget_dialect_pool_class�_pool_translate_kwargs�getZhandle_pool_kwargsZ_dialectrh �is_async� __class__�__name__r r � TypeError�joinZon_connect_urlr �listenZ_builtin_onconnectZengine_created) r rI Zstrat�ur@ Z entrypointrU r\ Z dialect_argsrn r^ Z dbapi_argsZ dbapi_methr) ZpluginZ cargs_tupr7 rb r& r8 Z pool_argsZtkZ engineclassZ engine_argsrk rt Zbuiltin_on_connectrz rL )re rf rg r[ rs ry rI rM rN \ s� A ��� � � � � �� � ��� #� � sqlalchemy.zDict[str, Any])� configuration�prefixrI rJ c s@ � �fdd�� D �}d|d< |� |� |�d�}t|fi |��S )a� Create a new Engine instance using a configuration dictionary. The dictionary is typically produced from a config file. The keys of interest to ``engine_from_config()`` should be prefixed, e.g. ``sqlalchemy.url``, ``sqlalchemy.echo``, etc. The 'prefix' argument indicates the prefix to be searched for. Each matching key (after the prefix is stripped) is treated as though it were the corresponding keyword argument to a :func:`_sa.create_engine` call. The only required key is (assuming the default prefix) ``sqlalchemy.url``, which provides the :ref:`database URL <database_urls>`. A select set of keyword arguments will be "coerced" to their expected type based on string values. The set of arguments is extensible per-dialect using the ``engine_config_types`` accessor. :param configuration: A dictionary (typically produced from a config file, but this is not a requirement). Items whose keys start with the value of 'prefix' will have that prefix stripped, and will then be passed to :func:`_sa.create_engine`. :param prefix: Prefix to match and then strip from keys in 'configuration'. :param kwargs: Each keyword argument to ``engine_from_config()`` itself overrides the corresponding item taken from the 'configuration' dictionary. Keyword arguments should *not* be prefixed. c s, i | ]$}|� ��r|t��d � � | �qS rK )� startswith�len)rm rW �r� r� rL rM � <dictcomp>/ s �z&engine_from_config.<locals>.<dictcomp>TrV r )r� rY rN )r� r� rI �optionsr rL r� rM �engine_from_config s " � r� )r8 r2 �pre_ping�size�recycle�reset_on_return�timeout�use_lifor" ) r r8 r2 r� r� r� r� r� r� rI rJ c K s d S rK rL ) r r8 r2 r� r� r� r� r� r� rI rL rL rM �create_pool_from_url: s r� c K s d S rK rL rO rL rL rM r� J s c K sB t D ] }||v r|�|�|t | < qt| fi |�ddi��}|jS )aZ Create a pool instance from the given url. If ``poolclass`` is not provided the pool class used is selected using the dialect specified in the URL. The arguments passed to :func:`_sa.create_pool_from_url` are identical to the pool argument passed to the :func:`_sa.create_engine` function. .. versionadded:: 2.0.10 rk F)r� rY rN r7 )r rI rW ry rL rL rM r� N s r9 r( r> r< Z pool_eventsr= r: r? )r2 r' r� r� �eventsr� r� r� )r� )1� __future__r r �typingr r r r r r r r r ri r r r| Z interfacesr rT r r r r r7 r r Zsqlr r � TYPE_CHECKINGr r r r r �logr r r r! r" Z util.typingr# rN Zdeprecated_paramsr� r� r� rL rL rL rM �<module> s� �X' � �-�(��
| ver. 1.6 |
Github
|
.
| PHP 8.2.30 | ??????????? ?????????: 0 |
proxy
|
phpinfo
|
???????????