PATH:
opt
/
hc_python
/
lib
/
python3.12
/
site-packages
/
sqlalchemy
/
event
/
__pycache__
� ���g� � � � d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddlm Z dd lm Z d d l m Z d d l mZ ej d � Z ej d� Z dd�Z dd�Z dd�Zdd�Zdd�Zy)z,Public API functions for the event system. � )� annotations)�Any)�Callable� )� _registrars)�_ET)� _EventKey)�_ListenerFnType� )�exc)�util�CANCEL� NO_RETVALc � � t | D ]& }|j | |� }|��t | |||� c S t j d|�d| �d�� �)NzNo such event 'z' for target '�')r � _accept_withr r �InvalidRequestError)�target� identifier�fn�evt_cls�tgts �E/opt/hc_python/lib64/python3.12/site-packages/sqlalchemy/event/api.py� _event_keyr sX � � �z�*���"�"�6�:�6�� �?� �V�Z��S�9� 9� +� �%�%�4>�� G� � � c �> � t | ||� j |i |�� y)aL Register a listener function for the given target. The :func:`.listen` function is part of the primary interface for the SQLAlchemy event system, documented at :ref:`event_toplevel`. e.g.:: from sqlalchemy import event from sqlalchemy.schema import UniqueConstraint def unique_constraint_name(const, table): const.name = "uq_%s_%s" % (table.name, list(const.columns)[0].name) event.listen( UniqueConstraint, "after_parent_attach", unique_constraint_name ) :param bool insert: The default behavior for event handlers is to append the decorated user defined function to an internal list of registered event listeners upon discovery. If a user registers a function with ``insert=True``, SQLAlchemy will insert (prepend) the function to the internal list upon discovery. This feature is not typically used or recommended by the SQLAlchemy maintainers, but is provided to ensure certain user defined functions can run before others, such as when :ref:`Changing the sql_mode in MySQL <mysql_sql_mode>`. :param bool named: When using named argument passing, the names listed in the function argument specification will be used as keys in the dictionary. See :ref:`event_named_argument_styles`. :param bool once: Private/Internal API usage. Deprecated. This parameter would provide that an event function would run only once per given target. It does not however imply automatic de-registration of the listener function; associating an arbitrarily high number of listeners without explicitly removing them will cause memory to grow unbounded even if ``once=True`` is specified. :param bool propagate: The ``propagate`` kwarg is available when working with ORM instrumentation and mapping events. See :class:`_ormevent.MapperEvents` and :meth:`_ormevent.MapperEvents.before_mapper_configured` for examples. :param bool retval: This flag applies only to specific event listeners, each of which includes documentation explaining when it should be used. By default, no listener ever requires a return value. However, some listeners do support special behaviors for return values, and include in their documentation that the ``retval=True`` flag is necessary for a return value to be processed. Event listener suites that make use of :paramref:`_event.listen.retval` include :class:`_events.ConnectionEvents` and :class:`_ormevent.AttributeEvents`. .. note:: The :func:`.listen` function cannot be called at the same time that the target event is being run. This has implications for thread safety, and also means an event cannot be added from inside the listener function for itself. The list of events to be run are present inside of a mutable collection that can't be changed during iteration. Event registration and removal is not intended to be a "high velocity" operation; it is a configurational operation. For systems that need to quickly associate and deassociate with events at high scale, use a mutable structure that is handled from inside of a single listener. .. seealso:: :func:`.listens_for` :func:`.remove` N)r �listen)r r r �args�kws r r r ) s# � �d .�J�v�z�2�&�-�-�t�:�r�:r c � � ���� d���� fd� }|S )a' Decorate a function as a listener for the given target + identifier. The :func:`.listens_for` decorator is part of the primary interface for the SQLAlchemy event system, documented at :ref:`event_toplevel`. This function generally shares the same kwargs as :func:`.listen`. e.g.:: from sqlalchemy import event from sqlalchemy.schema import UniqueConstraint @event.listens_for(UniqueConstraint, "after_parent_attach") def unique_constraint_name(const, table): const.name = "uq_%s_%s" % (table.name, list(const.columns)[0].name) A given function can also be invoked for only the first invocation of the event using the ``once`` argument:: @event.listens_for(Mapper, "before_configure", once=True) def on_config(): do_config() .. warning:: The ``once`` argument does not imply automatic de-registration of the listener function after it has been invoked a first time; a listener entry will remain associated with the target object. Associating an arbitrarily high number of listeners without explicitly removing them will cause memory to grow unbounded even if ``once=True`` is specified. .. seealso:: :func:`.listen` - general description of event listening c �* �� t ��| g���i ��� | S )N)r )r r r r r s ����r �decoratez listens_for.<locals>.decorate� s �� ��v�z�2�3��3��3�� r )r �Callable[..., Any]�returnr# � )r r r r r" s ```` r � listens_forr& ~ s �� �P� � �Or c �: � t | ||� j � y)a Remove an event listener. The arguments here should match exactly those which were sent to :func:`.listen`; all the event registration which proceeded as a result of this call will be reverted by calling :func:`.remove` with the same arguments. e.g.:: # if a function was registered like this... @event.listens_for(SomeMappedClass, "before_insert", propagate=True) def my_listener_function(*arg): pass # ... it's removed like this event.remove(SomeMappedClass, "before_insert", my_listener_function) Above, the listener function associated with ``SomeMappedClass`` was also propagated to subclasses of ``SomeMappedClass``; the :func:`.remove` function will revert all of these operations. .. note:: The :func:`.remove` function cannot be called at the same time that the target event is being run. This has implications for thread safety, and also means an event cannot be removed from inside the listener function for itself. The list of events to be run are present inside of a mutable collection that can't be changed during iteration. Event registration and removal is not intended to be a "high velocity" operation; it is a configurational operation. For systems that need to quickly associate and deassociate with events at high scale, use a mutable structure that is handled from inside of a single listener. .. seealso:: :func:`.listen` N)r �remove�r r r s r r( r( � s � �V �v�z�2�&�-�-�/r c �8 � t | ||� j � S )z=Return True if the given target/ident/fn is set up to listen.)r �containsr) s r r+ r+ � s � � �f�j�"� -� 6� 6� 8�8r N)r r r �strr r r$ z_EventKey[_ET]) r r r r, r r# r r r r r$ �None) r r r r, r r r r r$ z2Callable[[Callable[..., Any]], Callable[..., Any]])r r r r, r r# r$ r- )r r r r, r r# r$ �bool)�__doc__� __future__r �typingr r �baser �registryr r r � r r �symbolr r r r r& r( r+ r% r r �<module>r6 s� ��� #� � � � � � %� � � ����X� �� �D�K�K� � $� � � � � � �&5� �� �R;� �R;� �R;�&8�R;�AD�R;�LO�R;� �R;�j,� �,� �,�),�,�47�,�7�,�^+0�\9r
[-] registry.cpython-312.pyc
[edit]
[-] legacy.cpython-312.pyc
[edit]
[+]
..
[-] api.cpython-312.pyc
[edit]
[-] __init__.cpython-312.pyc
[edit]
[-] base.cpython-312.pyc
[edit]
[-] attr.cpython-312.pyc
[edit]