Scheduled weekly dependency update for week 18

[pyup-bot]

Update gevent from 21.1.2 to 25.4.2.

Changelog

25.4.2

===================


Features
--------

- Make gevent's ``queue`` classes subscriptable to match the standard library.
See :issue:`2102`.
- Make the c-ares resolver build on Windows.



----25.4.1 (2025-04-17)
===================


Features
--------

- Add a new environment variable and configuration setting to control
whether blocking reports are printed by the monitor thread.
See :issue:`2070`.
- Add initial support for Python 3.14a7. Earlier and later versions of
Python 3.14 may or may not work as expected.



Bugfixes
--------

- Fix using gevent's BackdoorServer with Unix sockets.
See :issue:`1769`.
- Monkey-patching the ``queue`` module (done by default in
``patch_all``) now patches ``Queue``, ``PriorityQueue``, and
``LifoQueue``. In addition to the general benefits of making all those
classes cooperative, this is known to solve a non-deterministic
deadlock with ``urllib3``.

In addition, ``Queue`` was renamed to ``SimpleQueue``; previously
``SimpleQueue`` was an alias for the undocumented
``queue._PySimpleQueue``. This makes ``SimpleQueue`` cooperative even
without monkey-patching.

Likewise, ``JoinableQueue`` was renamed to ``Queue``, providing the
``join`` method to all ``Queue`` objects, thus matching the standard
library. The old name remains for backwards compatibility.
See :issue:`1957`.

.. caution::
  Only the documented, tested (by the standard library), attributes are identical between
  the standard library and gevent ``Queue`` implementations.
  Internal implementation details are very different, and using
  undocumented, untested details such as the internal ``Condition``
  object ``all_tasks_done`` instead of the documented, tested
  ``join`` method will fail with this change.

  If you have code that relies on undocumented implementation
  details that cannot bo ported to the documented interface, please
  file an issue.


- Do not assume that ``threading.get_native_id`` exists. This improves
support for untested platforms.
See :issue:`2053`.
- Do not use pywsgi in a security-conscious environment.

Fix one security issue related to HTTP 100 Continue handling.
See :issue:`2075`.

24.11.1

====================


Bugfixes
--------

- Remove some legacy code that supported Python 2 for compatibility with
the upcoming releases of Cython 3.1.

Also, the ``PeriodicMonitorThreadStartedEvent`` now properly
implements the ``IPeriodicMonitorThreadStartedEvent`` interface.
The ``EventLoopBlocked`` event includes the hub which was blocked,
and it is notified before the report is printed so that event
listeners can modify the report.
See :issue:`2076`.

24.10.3

====================


Bugfixes
--------

- Fix clearing stack frames on Python 3.13. This is invoked when you
fork after having used the thread pool.
See :issue:`2067`.
- Distribute manylinux2014 wheels for x86_64.
See :issue:`2068`.
- Stop switching to the hub in the after fork hook in a child process. This could lead to strange behaviour, and is different than what all other versions of Python do.

24.10.2

====================


Bugfixes
--------

- Workaround a Cython bug compiling on GCC14.
See :issue:`2049`.

24.10.1

====================


Features
--------

- Update the bundled c-ares to 1.33.1.

- Add support for Python 3.13.

- The functions and classes in ``gevent.subprocess`` no longer accept
 ``stdout=STDOUT`` and raise a ``ValueError``.

Several additions and changes to the ``queue`` module, including:

- ``Queue.shutdown`` is available on all versions of Python.
- ``LifoQueue`` is now a joinable queue.

- gevent.monkey changed from a module to a package. The public API
remains the same.

For this release, private APIs (undocumented, marked internal, or
beginning with an underscore) are also preserved. However, these may
be changed or removed at any time in the future. If you are using one
of these APIs and cannot replace it, please contact the gevent team.



Bugfixes
--------

- For platforms that don't have ``socketpair``, upgrade our fallback
code to avoid a security issue.
See :issue:`2048`.


Deprecations and Removals
-------------------------

- Remove support for Python 3.8, which has reached the end of its
support lifecycle.
See :issue:`remove_py38`.

24.2.1

===================


Bugfixes
--------

- Add support for Python patch releases 3.11.8 and 3.12.2, which changed
internal details of threading.

As a result of these changes, note that it is no longer possible to
change the ``__class__`` of a ``gevent.threading._DummyThread``
object on those versions.

See :issue:`2020`.

Other
-----

Other updates for compatibility with the standard library include:

- Errors raised from ``subprocess.Popen`` may not have a filename set.
- ``SSLSocket.recv_into`` and ``SSLSocket.read`` no longer require the
 buffer to implement ``len`` and now work with buffers whose size is
 not 1.
- gh-108310: Fix CVE-2023-40217: Check for & avoid the ssl pre-close
 flaw.

In addition:

- Drop ``setuptools`` to a soft test dependency.
- Drop support for very old versions of CFFI.
- Update bundled c-ares from 1.19.1 to 1.26.0.
- Locks created by gevent, but acquired from multiple different
 threads (not recommended), no longer spin to implement timeouts
 and interruptible blocking. Instead, they use the native
 functionality of the Python 3 lock. This may improve some scenarios.
 See :issue:`2013`.

23.9.1

===================


Bugfixes
--------

- Require greenlet 3.0 on Python 3.11 and Python 3.12; greenlet 3.0 is
recommended for all platforms. This fixes a number of obscure crashes
on all versions of Python, as well as fixing a fairly common problem
on Python 3.11+ that could manifest as either a crash or as a
``SystemError``.
See :issue:`1985`.


----

23.9.0.post1

=========================

- Fix Windows wheel builds.
- Fix macOS wheel builds.

23.9.0

===================


Bugfixes
--------

- Make ``gevent.select.select`` accept arbitrary iterables, not just
sequences. That is, you can now pass in a generator of file
descriptors instead of a realized list. Internally, arbitrary
iterables are copied into lists. This better matches what the standard
library does. Thanks to David Salvisberg.
See :issue:`1979`.
- On Python 3.11 and newer, opt out of Cython's fast exception
manipulation, which *may* be causing problems in certain circumstances
when combined with greenlets.

On all versions of Python, adjust some error handling in the default
C-based loop. This fixes several assertion failures on debug versions
of CPython. Hopefully it has a positive impact under real conditions.
See :issue:`1985`.
- Make ``gevent.pywsgi`` comply more closely with the HTTP specification
for chunked transfer encoding. In particular, we are much stricter
about trailers, and trailers that are invalid (too long or featuring
disallowed characters) forcibly close the connection to the client
*after* the results have been sent.

Trailers otherwise continue to be ignored and are not available to the
WSGI application.

Previously, carefully crafted invalid trailers in chunked requests on
keep-alive connections might appear as two requests to
``gevent.pywsgi``. Because this was handled exactly as a normal
keep-alive connection with two requests, the WSGI application should
handle it normally. However, if you were counting on some upstream
server to filter incoming requests based on paths or header fields,
and the upstream server simply passed trailers through without
validating them, then this embedded second request would bypass those
checks. (If the upstream server validated that the trailers meet the
HTTP specification, this could not occur, because characters that are
required in an HTTP request, like a space, are not allowed in
trailers.) CVE-2023-41419 was reserved for this.

Our thanks to the original reporters, Keran Mu
(mkr22mails.tsinghua.edu.cn) and Jianjun Chen
(jianjuntsinghua.edu.cn), from Tsinghua University and Zhongguancun
Laboratory.
See :issue:`1989`.


----

23.7.0

===================


Features
--------

- Add preliminary support for Python 3.12, using greenlet 3.0a1. This
is somewhat tricky to build from source at this time, and there is
one known issue: On Python 3.12b3, dumping tracebacks of greenlets
is not available.
:issue:`1969`.
- Update the bundled c-ares version to 1.19.1.
See :issue:`1947`.


Bugfixes
--------

- Fix an edge case connecting a non-blocking ``SSLSocket`` that could result
in an AttributeError. In a change to match the standard library,
calling ``sock.connect_ex()`` on a subclass of ``socket`` no longer
calls the subclass's ``connect`` method.

Initial fix by Priyankar Jain.
See :issue:`1932`.
- Make gevent's ``FileObjectThread`` (mostly used on Windows) implement
``readinto`` cooperatively. PR by Kirill Smelkov.
See :issue:`1948`.
- Work around an ``AttributeError`` during cyclic garbage collection
when Python finalizers (``__del__`` and the like) attempt to use
gevent APIs. This is not a recommended practice, and it is unclear if
catching this ``AttributeError`` will fix any problems or just shift
them. (If we could determine the root situation that results in this
cycle, we might be able to solve it.)
See :issue:`1961`.


Deprecations and Removals
-------------------------

- Remove support for obsolete Python versions. This is everything prior
to 3.8.

Related changes include:

- Stop using ``pkg_resources`` to find entry points (plugins).
 Instead, use ``importlib.metadata``.
- Honor ``sys.unraisablehook`` when a callback function produces an
 exception, and handling the exception in the hub *also* produces an
 exception. In older versions, these would be simply printed.
- ``setup.py`` no longer includes the ``setup_requires`` keyword.
 Installation with a tool that understands ``pyproject.toml`` is
 recommended.
- The bundled tblib has been updated to version 2.0.


----

22.10.2

====================


Bugfixes
--------

- Update to greenlet 2.0. This fixes a deallocation issue that required
a change in greenlet's ABI. The design of greenlet 2.0 is intended to
prevent future fixes and enhancements from requiring an ABI change,
making it easier to update gevent and greenlet independently.

.. caution::

  greenlet 2.0 requires a modern-ish C++ compiler. This may mean
  certain older platforms are no longer supported.
  See :issue:`1909`.


----

22.10.1

====================


Features
--------

- Update bundled libuv to 1.44.2.
See :issue:`1913`.


Misc
----

- See :issue:`1898`., See :issue:`1910`., See :issue:`1915`.


----

22.08.0

====================


Features
--------

- Windows: Test and provide binary wheels for PyPy3.7.

Note that there may be issues with subprocesses, signals, and it may
be slow.
See :issue:`1798`.
- Upgrade embedded c-ares to 1.18.1.
See :issue:`1847`.
- Upgrade bundled libuv to 1.42.0 from 1.40.0.
See :issue:`1851`.
- Added preliminary support for Python 3.11 (rc2 and later).

Some platforms may or may not have binary wheels at this time.

.. important:: Support for legacy versions of Python, including 2.7
              and 3.6, will be ending soon. The
              maintenance burden has become too great and the
              maintainer's time is too limited.

              Ideally, there will be a release of gevent compatible
              with a final release of greenlet 2.0 that still
              supports those legacy versions, but that may not be
              possible; this may be the final release to support them.

:class:`gevent.threadpool.ThreadPool` can now optionally expire idle
threads. This is used by default in the implicit thread pool used for
DNS requests and other user-submitted tasks; other uses of a
thread-pool need to opt-in to this.
See :issue:`1867`.


Bugfixes
--------

- Truly disable the effects of compiling with ``-ffast-math``.
See :issue:`1864`.


----

21.12.0

====================


Features
--------

- Update autoconf files for Apple Silicon Macs. Note that while there
are reports of compiling gevent on Apple Silicon Macs now, this is
*not* a tested configuration. There may be some remaining issues with
CFFI on some systems as well.
See :issue:`1721`.
- Build and upload CPython 3.10 binary manylinux wheels.

Unfortunately, this required us to stop building and uploading CPython
2.7 binary manylinux wheels. Binary wheels for 2.7 continue to be
available for Windows and macOS.
See :issue:`1822`.
- Test and distribute musllinux_1_1 wheels.
See :issue:`1837`.
- Update the tested versions of PyPy2 and PyPy3. For PyPy2, there should
be no user visible changes, but for PyPy3, support has moved from
Python 3.6 to Python 3.7.
See :issue:`1843`.


Bugfixes
--------

- Try to avoid linking to two different Python runtime DLLs on Windows.
See :issue:`1814`.
- Stop compiling manylinux wheels with ``-ffast-math.`` This was
implicit in ``-Ofast``, but could alter the global state of the
process. Analysis and fix thanks to Ilya Konstantinov.
See :issue:`1820`.
- Fix hanging the interpreter on shutdown if gevent monkey patching
occurred on a non-main thread in Python 3.9.8 and above. (Note that
this is not a recommended practice.)
See :issue:`1839`.


----

21.8.0

===================


Features
--------

- Update the embedded c-ares from 1.16.1 to 1.17.1.
See :issue:`1758`.
- Add support for Python 3.10rc1 and newer.

As part of this, the minimum required greenlet version was increased
to 1.1.0 (on CPython), and the minimum version of Cython needed to
build gevent from a source checkout is 3.0a9.

Note that the dnspython resolver is not available on Python 3.10.
See :issue:`1790`.
- Update from Cython 3.0a6 to 3.0a9.
See :issue:`1801`.


Misc
----

- See :issue:`1789`.


----

Links

• PyPI: https://pypi.org/project/gevent
• Changelog: https://data.safetycli.com/changelogs/gevent/
• Homepage: http://www.gevent.org/

Update sqlalchemy from 2.0.40 to 2.0.40.

Changelog

2.0.40

:released: March 27, 2025

 .. change::
     :tags: usecase, postgresql
     :tickets: 11595

     Added support for specifying a list of columns for ``SET NULL`` and ``SET
     DEFAULT`` actions of ``ON DELETE`` clause of foreign key definition on
     PostgreSQL.  Pull request courtesy Denis Laxalde.

     .. seealso::

         :ref:`postgresql_constraint_options`

 .. change::
     :tags: bug, orm
     :tickets: 12329

     Fixed regression which occurred as of 2.0.37 where the checked
     :class:`.ArgumentError` that's raised when an inappropriate type or object
     is used inside of a :class:`.Mapped` annotation would raise ``TypeError``
     with "boolean value of this clause is not defined" if the object resolved
     into a SQL expression in a boolean context, for programs where future
     annotations mode was not enabled.  This case is now handled explicitly and
     a new error message has also been tailored for this case.  In addition, as
     there are at least half a dozen distinct error scenarios for intepretation
     of the :class:`.Mapped` construct, these scenarios have all been unified
     under a new subclass of :class:`.ArgumentError` called
     :class:`.MappedAnnotationError`, to provide some continuity between these
     different scenarios, even though specific messaging remains distinct.

 .. change::
     :tags: bug, mysql
     :tickets: 12332

     Support has been re-added for the MySQL-Connector/Python DBAPI using the
     ``mysql+mysqlconnector://`` URL scheme.   The DBAPI now works against
     modern MySQL versions as well as MariaDB versions (in the latter case it's
     required to pass charset/collation explicitly).   Note however that
     server side cursor support is disabled due to unresolved issues with this
     driver.

 .. change::
     :tags: bug, sql
     :tickets: 12363

     Fixed issue in :class:`.CTE` constructs involving multiple DDL
     :class:`_sql.Insert` statements with multiple VALUES parameter sets where the
     bound parameter names generated for these parameter sets would conflict,
     generating a compile time error.


 .. change::
     :tags: bug, sqlite
     :tickets: 12425

     Expanded the rules for when to apply parenthesis to a server default in DDL
     to suit the general case of a default string that contains non-word
     characters such as spaces or operators and is not a string literal.

 .. change::
     :tags: bug, mysql
     :tickets: 12425

     Fixed issue in MySQL server default reflection where a default that has
     spaces would not be correctly reflected.  Additionally, expanded the rules
     for when to apply parenthesis to a server default in DDL to suit the
     general case of a default string that contains non-word characters such as
     spaces or operators and is not a string literal.


 .. change::
     :tags: usecase, postgresql
     :tickets: 12432

     When building a PostgreSQL ``ARRAY`` literal using
     :class:`_postgresql.array` with an empty ``clauses`` argument, the
     :paramref:`_postgresql.array.type_` parameter is now significant in that it
     will be used to render the resulting ``ARRAY[]`` SQL expression with a
     cast, such as ``ARRAY[]::INTEGER``. Pull request courtesy Denis Laxalde.

 .. change::
     :tags: sql, usecase
     :tickets: 12450

     Implemented support for the GROUPS frame specification in window functions
     by adding :paramref:`_sql.over.groups` option to :func:`_sql.over`
     and :meth:`.FunctionElement.over`. Pull request courtesy Kaan Dikmen.

 .. change::
     :tags: bug, sql
     :tickets: 12451

     Fixed regression caused by :ticket:`7471` leading to a SQL compilation
     issue where name disambiguation for two same-named FROM clauses with table
     aliasing in use at the same time would produce invalid SQL in the FROM
     clause with two "AS" clauses for the aliased table, due to double aliasing.

 .. change::
     :tags: bug, asyncio
     :tickets: 12471

     Fixed issue where :meth:`.AsyncSession.get_transaction` and
     :meth:`.AsyncSession.get_nested_transaction` would fail with
     ``NotImplementedError`` if the "proxy transaction" used by
     :class:`.AsyncSession` were garbage collected and needed regeneration.

 .. change::
     :tags: bug, orm
     :tickets: 12473

     Fixed regression in ORM Annotated Declarative class interpretation caused
     by ``typing_extension==4.13.0`` that introduced a different implementation
     for ``TypeAliasType`` while SQLAlchemy assumed that it would be equivalent
     to the ``typing`` version, leading to pep-695 type annotations not
     resolving to SQL types as expected.

.. changelog::

2.0.39

:released: March 11, 2025

 .. change::
     :tags: bug, postgresql
     :tickets: 11751

     Add SQL typing to reflection query used to retrieve a the structure
     of IDENTITY columns, adding explicit JSON typing to the query to suit
     unusual PostgreSQL driver configurations that don't support JSON natively.

 .. change::
     :tags: bug, postgresql

     Fixed issue affecting PostgreSQL 17.3 and greater where reflection of
     domains with "NOT NULL" as part of their definition would include an
     invalid constraint entry in the data returned by
     :meth:`_postgresql.PGInspector.get_domains` corresponding to an additional
     "NOT NULL" constraint that isn't a CHECK constraint; the existing
     ``"nullable"`` entry in the dictionary already indicates if the domain
     includes a "not null" constraint.   Note that such domains also cannot be
     reflected on PostgreSQL 17.0 through 17.2 due to a bug on the PostgreSQL
     side; if encountering errors in reflection of domains which include NOT
     NULL, upgrade to PostgreSQL server 17.3 or greater.

 .. change::
     :tags: typing, usecase
     :tickets: 11922

     Support generic types for compound selects (:func:`_sql.union`,
     :func:`_sql.union_all`, :meth:`_sql.Select.union`,
     :meth:`_sql.Select.union_all`, etc) returning the type of the first select.
     Pull request courtesy of Mingyu Park.

 .. change::
     :tags: bug, postgresql
     :tickets: 12060

     Fixed issue in PostgreSQL network types :class:`_postgresql.INET`,
     :class:`_postgresql.CIDR`, :class:`_postgresql.MACADDR`,
     :class:`_postgresql.MACADDR8` where sending string values to compare to
     these types would render an explicit CAST to VARCHAR, causing some SQL /
     driver combinations to fail.  Pull request courtesy Denis Laxalde.

 .. change::
     :tags: bug, orm
     :tickets: 12326

     Fixed bug where using DML returning such as :meth:`.Insert.returning` with
     an ORM model that has :func:`_orm.column_property` constructs that contain
     subqueries would fail with an internal error.

 .. change::
     :tags: bug, orm
     :tickets: 12328

     Fixed bug in ORM enabled UPDATE (and theoretically DELETE) where using a
     multi-table DML statement would not allow ORM mapped columns from mappers
     other than the primary UPDATE mapper to be named in the RETURNING clause;
     they would be omitted instead and cause a column not found exception.

 .. change::
     :tags: bug, asyncio
     :tickets: 12338

     Fixed bug where :meth:`_asyncio.AsyncResult.scalar`,
     :meth:`_asyncio.AsyncResult.scalar_one_or_none`, and
     :meth:`_asyncio.AsyncResult.scalar_one` would raise an ``AttributeError``
     due to a missing internal attribute.  Pull request courtesy Allen Ho.

 .. change::
     :tags: bug, orm
     :tickets: 12357

     Fixed issue where the "is ORM" flag of a :func:`.select` or other ORM
     statement would not be propagated to the ORM :class:`.Session` based on a
     multi-part operator expression alone, e.g. such as ``Cls.attr + Cls.attr +
     Cls.attr`` or similar, leading to ORM behaviors not taking place for such
     statements.

 .. change::
     :tags: bug, orm
     :tickets: 12364

     Fixed issue where using :func:`_orm.aliased` around a :class:`.CTE`
     construct could cause inappropriate "duplicate CTE" errors in cases where
     that aliased construct appeared multiple times in a single statement.

 .. change::
     :tags: bug, sqlite
     :tickets: 12368

     Fixed issue that omitted the comma between multiple SQLite table extension
     clauses, currently ``WITH ROWID`` and ``STRICT``, when both options
     :paramref:`.Table.sqlite_with_rowid` and  :paramref:`.Table.sqlite_strict`
     were configured at their non-default settings at the same time.  Pull
     request courtesy david-fed.

 .. change::
     :tags: bug, sql
     :tickets: 12382

     Added new parameters :paramref:`.AddConstraint.isolate_from_table` and
     :paramref:`.DropConstraint.isolate_from_table`, defaulting to True, which
     both document and allow to be controllable the long-standing behavior of
     these two constructs blocking the given constraint from being included
     inline within the "CREATE TABLE" sequence, under the assumption that
     separate add/drop directives were to be used.

 .. change::
     :tags: bug, postgresql
     :tickets: 12417

     Fixed compiler issue in the PostgreSQL dialect where incorrect keywords
     would be passed when using "FOR UPDATE OF" inside of a subquery.

.. changelog::

2.0.38

:released: February 6, 2025

 .. change::
     :tags: postgresql, usecase, asyncio
     :tickets: 12077

     Added an additional ``asyncio.shield()`` call within the connection
     terminate process of the asyncpg driver, to mitigate an issue where
     terminate would be prevented from completing under the anyio concurrency
     library.

 .. change::
     :tags: bug, dml, mariadb, mysql
     :tickets: 12117

     Fixed a bug where the MySQL statement compiler would not properly compile
     statements where :meth:`_mysql.Insert.on_duplicate_key_update` was passed
     values that included ORM-mapped attributes (e.g.
     :class:`InstrumentedAttribute` objects) as keys. Pull request courtesy of
     mingyu.

 .. change::
     :tags: bug, postgresql
     :tickets: 12159

     Adjusted the asyncpg connection wrapper so that the
     ``connection.transaction()`` call sent to asyncpg sends ``None`` for
     ``isolation_level`` if not otherwise set in the SQLAlchemy dialect/wrapper,
     thereby allowing asyncpg to make use of the server level setting for
     ``isolation_level`` in the absense of a client-level setting. Previously,
     this behavior of asyncpg was blocked by a hardcoded ``read_committed``.

 .. change::
     :tags: bug, sqlite, aiosqlite, asyncio, pool
     :tickets: 12285

     Changed default connection pool used by the ``aiosqlite`` dialect
     from :class:`.NullPool` to :class:`.AsyncAdaptedQueuePool`; this change
     should have been made when 2.0 was first released as the ``pysqlite``
     dialect was similarly changed to use :class:`.QueuePool` as detailed
     in :ref:`change_7490`.


 .. change::
     :tags: bug, engine
     :tickets: 12289

     Fixed event-related issue where invoking :meth:`.Engine.execution_options`
     on a :class:`.Engine` multiple times while making use of event-registering
     parameters such as ``isolation_level`` would lead to internal errors
     involving event registration.

 .. change::
     :tags: bug, sql
     :tickets: 12302

     Reorganized the internals by which the ``.c`` collection on a
     :class:`.FromClause` gets generated so that it is resilient against the
     collection being accessed in concurrent fashion.   An example is creating a
     :class:`.Alias` or :class:`.Subquery` and accessing it as a module level
     variable.  This impacts the Oracle dialect which uses such module-level
     global alias objects but is of general use as well.

 .. change::
     :tags: bug, sql
     :tickets: 12314

     Fixed SQL composition bug which impacted caching where using a ``None``
     value inside of an ``in_()`` expression would bypass the usual "expanded
     bind parameter" logic used by the IN construct, which allows proper caching
     to take place.


.. changelog::

2.0.37

:released: January 9, 2025

 .. change::
     :tags: usecase, mariadb
     :tickets: 10720

     Added sql types ``INET4`` and ``INET6`` in the MariaDB dialect.  Pull
     request courtesy Adam Žurek.

 .. change::
     :tags: bug, orm
     :tickets: 11370

     Fixed issue regarding ``Union`` types that would be present in the
     :paramref:`_orm.registry.type_annotation_map` of a :class:`_orm.registry`
     or declarative base class, where a :class:`.Mapped` element that included
     one of the subtypes present in that ``Union`` would be matched to that
     entry, potentially ignoring other entries that matched exactly.   The
     correct behavior now takes place such that an entry should only match in
     :paramref:`_orm.registry.type_annotation_map` exactly, as a ``Union`` type
     is a self-contained type. For example, an attribute with ``Mapped[float]``
     would previously match to a :paramref:`_orm.registry.type_annotation_map`
     entry ``Union[float, Decimal]``; this will no longer match and will now
     only match to an entry that states ``float``. Pull request courtesy Frazer
     McLean.

 .. change::
     :tags: bug, postgresql
     :tickets: 11724

     Fixes issue in :meth:`.Dialect.get_multi_indexes` in the PostgreSQL
     dialect, where an error would be thrown when attempting to use alembic with
     a vector index from the pgvecto.rs extension.

 .. change::
     :tags:  usecase, mysql, mariadb
     :tickets: 11764

     Added support for the ``LIMIT`` clause with ``DELETE`` for the MySQL and
     MariaDB dialects, to complement the already present option for
     ``UPDATE``. The :meth:`.Delete.with_dialect_options` method of the
     :func:`.delete` construct accepts parameters for ``mysql_limit`` and
     ``mariadb_limit``, allowing users to specify a limit on the number of rows
     deleted. Pull request courtesy of Pablo Nicolás Estevez.


 .. change::
     :tags:  bug, mysql, mariadb

     Added logic to ensure that the ``mysql_limit`` and ``mariadb_limit``
     parameters of :meth:`.Update.with_dialect_options` and
     :meth:`.Delete.with_dialect_options` when compiled to string will only
     compile if the parameter is passed as an integer; a ``ValueError`` is
     raised otherwise.

 .. change::
     :tags: bug, orm
     :tickets: 11944

     Fixed bug in how type unions were handled within
     :paramref:`_orm.registry.type_annotation_map` as well as
     :class:`._orm.Mapped` that made the lookup behavior of ``a | b`` different
     from that of ``Union[a, b]``.

 .. change::
     :tags: bug, orm
     :tickets: 11955

     Consistently handle ``TypeAliasType`` (defined in PEP 695) obtained with
     the ``type X = int`` syntax introduced in python 3.12. Now in all cases one
     such alias must be explicitly added to the type map for it to be usable
     inside :class:`.Mapped`. This change also revises the approach added in
     :ticket:`11305`, now requiring the ``TypeAliasType`` to be added to the
     type map. Documentation on how unions and type alias types are handled by
     SQLAlchemy has been added in the
     :ref:`orm_declarative_mapped_column_type_map` section of the documentation.

 .. change::
     :tags: feature, oracle
     :tickets: 12016

     Added new table option ``oracle_tablespace`` to specify the ``TABLESPACE``
     option when creating a table in Oracle. This allows users to define the
     tablespace in which the table should be created. Pull request courtesy of
     Miguel Grillo.

 .. change::
     :tags: orm, bug
     :tickets: 12019

     Fixed regression caused by an internal code change in response to recent
     Mypy releases that caused the very unusual case of a list of ORM-mapped
     attribute expressions passed to :meth:`.ColumnOperators.in_` to no longer
     be accepted.

 .. change::
     :tags: oracle, usecase
     :tickets: 12032

     Use the connection attribute ``max_identifier_length`` available
     in oracledb since version 2.5 when determining the identifier length
     in the Oracle dialect.

 .. change::
     :tags: bug, sql
     :tickets: 12084

     Fixed issue in "lambda SQL" feature where the tracking of bound parameters
     could be corrupted if the same lambda were evaluated across multiple
     compile phases, including when using the same lambda across multiple engine
     instances or with statement caching disabled.


 .. change::
     :tags: usecase, postgresql
     :tickets: 12093

     The :class:`_postgresql.Range` type now supports
     :meth:`_postgresql.Range.__contains__`. Pull request courtesy of Frazer
     McLean.

 .. change::
     :tags: bug, oracle
     :tickets: 12100

     Fixed compilation of ``TABLE`` function when used in a ``FROM`` clause in
     Oracle Database dialect.

 .. change::
     :tags: bug, oracle
     :tickets: 12150

     Fixed issue in oracledb / cx_oracle dialects where output type handlers for
     ``CLOB`` were being routed to ``NVARCHAR`` rather than ``VARCHAR``, causing
     a double conversion to take place.


 .. change::
     :tags: bug, postgresql
     :tickets: 12170

     Fixed issue where creating a table with a primary column of
     :class:`_sql.SmallInteger` and using the asyncpg driver would result in
     the type being compiled to ``SERIAL`` rather than ``SMALLSERIAL``.

 .. change::
     :tags: bug, orm
     :tickets: 12207

     Fixed issues in type handling within the
     :paramref:`_orm.registry.type_annotation_map` feature which prevented the
     use of unions, using either pep-604 or ``Union`` syntaxes under future
     annotations mode, which contained multiple generic types as elements from
     being correctly resolvable.

 .. change::
     :tags: bug, orm
     :tickets: 12216

     Fixed issue in event system which prevented an event listener from being
     attached and detached from multiple class-like objects, namely the
     :class:`.sessionmaker` or :class:`.scoped_session` targets that assign to
     :class:`.Session` subclasses.


 .. change::
     :tags: bug, postgresql
     :tickets: 12220

     Adjusted the asyncpg dialect so that an empty SQL string, which is valid
     for PostgreSQL server, may be successfully processed at the dialect level,
     such as when using :meth:`.Connection.exec_driver_sql`. Pull request
     courtesy Andrew Jackson.


 .. change::
     :tags: usecase, sqlite
     :tickets: 7398

     Added SQLite table option to enable ``STRICT`` tables. Pull request
     courtesy of Guilherme Crocetti.

.. changelog::

2.0.36

:released: October 15, 2024

 .. change::
     :tags: bug, schema
     :tickets: 11317

     Fixed bug where SQL functions passed to
     :paramref:`_schema.Column.server_default` would not be rendered with the
     particular form of parenthesization now required by newer versions of MySQL
     and MariaDB. Pull request courtesy of huuya.

 .. change::
     :tags: bug, orm
     :tickets: 11912

     Fixed bug in ORM bulk update/delete where using RETURNING with bulk
     update/delete in combination with ``populate_existing`` would fail to
     accommodate the ``populate_existing`` option.

 .. change::
     :tags: bug, orm
     :tickets: 11917

     Continuing from :ticket:`11912`, columns marked with
     :paramref:`.mapped_column.onupdate`,
     :paramref:`.mapped_column.server_onupdate`, or :class:`.Computed` are now
     refreshed in ORM instances when running an ORM enabled UPDATE with WHERE
     criteria, even if the statement does not use RETURNING or
     ``populate_existing``.

 .. change::
     :tags: usecase, orm
     :tickets: 11923

     Added new parameter :paramref:`_orm.mapped_column.hash` to ORM constructs
     such as :meth:`_orm.mapped_column`, :meth:`_orm.relationship`, etc.,
     which is interpreted for ORM Native Dataclasses in the same way as other
     dataclass-specific field parameters.

 .. change::
     :tags: bug, postgresql, reflection
     :tickets: 11961

     Fixed bug in reflection of table comments where unrelated text would be
     returned if an entry in the ``pg_description`` table happened to share the
     same oid (objoid) as the table being reflected.

 .. change::
     :tags: bug, orm
     :tickets: 11965

     Fixed regression caused by fixes to joined eager loading in :ticket:`11449`
     released in 2.0.31, where a particular joinedload case could not be
     asserted correctly.   We now have an example of that case so the assertion
     has been repaired to allow for it.


 .. change::
     :tags: orm, bug
     :tickets: 11973

     Improved the error message emitted when trying to map as dataclass a class
     while also manually providing the ``__table__`` attribute.
     This usage is currently not supported.

 .. change::
     :tags: mysql, performance
     :tickets: 11975

     Improved a query used for the MySQL 8 backend when reflecting foreign keys
     to be better optimized.   Previously, for a database that had millions of
     columns across all tables, the query could be prohibitively slow; the query
     has been reworked to take better advantage of existing indexes.

 .. change::
     :tags: usecase, sql
     :tickets: 11978

     Datatypes that are binary based such as :class:`.VARBINARY` will resolve to
     :class:`.LargeBinary` when the :meth:`.TypeEngine.as_generic()` method is
     called.

 .. change::
     :tags: postgresql, bug
     :tickets: 11994

     The :class:`.postgresql.JSON` and :class:`.postgresql.JSONB` datatypes will
     now render a "bind cast" in all cases for all PostgreSQL backends,
     including psycopg2, whereas previously it was only enabled for some
     backends.   This allows greater accuracy in allowing the database server to
     recognize when a string value is to be interpreted as JSON.

 .. change::
     :tags: bug, orm
     :tickets: 11995

     Refined the check which the ORM lazy loader uses to detect "this would be
     loading by primary key and the primary key is NULL, skip loading" to take
     into account the current setting for the
     :paramref:`.orm.Mapper.allow_partial_pks` parameter. If this parameter is
     ``False``, then a composite PK value that has partial NULL elements should
     also be skipped.   This can apply to some composite overlapping foreign key
     configurations.


 .. change::
     :tags: bug, orm
     :tickets: 11997

     Fixed bug in ORM "update with WHERE clause" feature where an explicit
     ``.returning()`` would interfere with the "fetch" synchronize strategy due
     to an assumption that the ORM mapped class featured the primary key columns
     in a specific position within the RETURNING.  This has been fixed to use
     appropriate ORM column targeting.

 .. change::
     :tags: bug, sql, regression
     :tickets: 12002

     Fixed regression from 1.4 where some datatypes such as those derived from
     :class:`.TypeDecorator` could not be pickled when they were part of a
     larger SQL expression composition due to internal supporting structures
     themselves not being pickleable.

.. changelog::

2.0.35

:released: September 16, 2024

 .. change::
     :tags: bug, orm, typing
     :tickets: 11820

     Fixed issue where it was not possible to use ``typing.Literal`` with
     ``Mapped[]`` on Python 3.8 and 3.9.  Pull request courtesy Frazer McLean.

 .. change::
     :tags: bug, sqlite, regression
     :tickets: 11840

     The changes made for SQLite CHECK constraint reflection in versions 2.0.33
     and 2.0.34 , :ticket:`11832` and :ticket:`11677`, have now been fully
     reverted, as users continued to identify existing use cases that stopped
     working after this change.   For the moment, because SQLite does not
     provide any consistent way of delivering information about CHECK
     constraints, SQLAlchemy is limited in what CHECK constraint syntaxes can be
     reflected, including that a CHECK constraint must be stated all on a
     single, independent line (or inline on a column definition)  without
     newlines, tabs in the constraint definition or unusual characters in the
     constraint name.  Overall, reflection for SQLite is tailored towards being
     able to reflect CREATE TABLE statements that were originally created by
     SQLAlchemy DDL constructs.  Long term work on a DDL parser that does not
     rely upon regular expressions may eventually improve upon this situation.
     A wide range of additional cross-dialect CHECK constraint reflection tests
     have been added as it was also a bug that these changes did not trip any
     existing tests.

 .. change::
     :tags: orm, bug
     :tickets: 11849

     Fixed issue in ORM evaluator where two datatypes being evaluated with the
     SQL concatenator operator would not be checked for
     :class:`.UnevaluatableError` based on their datatype; this missed the case
     of :class:`_postgresql.JSONB` values being used in a concatenate operation
     which is supported by PostgreSQL as well as how SQLAlchemy renders the SQL
     for this operation, but does not work at the Python level. By implementing
     :class:`.UnevaluatableError` for this combination, ORM update statements
     will now fall back to "expire" when a concatenated JSON value used in a SET
     clause is to be synchronized to a Python object.

 .. change::
     :tags: bug, orm
     :tickets: 11853

     An warning is emitted if :func:`_orm.joinedload` or
     :func:`_orm.subqueryload` are used as a top level option against a
     statement that is not a SELECT statement, such as with an
     ``insert().returning()``.   There are no JOINs in INSERT statements nor is
     there a "subquery" that can be repurposed for subquery eager loading, and
     for UPDATE/DELETE joinedload does not support these either, so it is never
     appropriate for this use to pass silently.

 .. change::
     :tags: bug, orm
     :tickets: 11855

     Fixed issue where using loader options such as :func:`_orm.selectinload`
     with additional criteria in combination with ORM DML such as
     :func:`_sql.insert` with RETURNING would not correctly set up internal
     contexts required for caching to work correctly, leading to incorrect
     results.

 .. change::
     :tags: bug, mysql
     :tickets: 11870

     Fixed issue in mariadbconnector dialect where query string arguments that
     weren't checked integer or boolean arguments would be ignored, such as
     string arguments like ``unix_socket``, etc.  As part of this change, the
     argument parsing for particular elements such as ``client_flags``,
     ``compress``, ``local_infile`` has been made more consistent across all
     MySQL / MariaDB dialect which accept each argument. Pull request courtesy
     Tobias Alex-Petersen.


.. changelog::

2.0.34

:released: September 4, 2024

 .. change::
     :tags: bug, orm
     :tickets: 11831

     Fixed regression caused by issue :ticket:`11814` which broke support for
     certain flavors of :pep:`593` ``Annotated`` in the type_annotation_map when
     builtin types such as ``list``, ``dict`` were used without an element type.
     While this is an incomplete style of typing, these types nonetheless
     previously would be located in the type_annotation_map correctly.

 .. change::
     :tags: bug, sqlite
     :tickets: 11832

     Fixed regression in SQLite reflection caused by :ticket:`11677` which
     interfered with reflection for CHECK constraints that were followed
     by other kinds of constraints within the same table definition.   Pull
     request courtesy Harutaka Kawamura.


.. changelog::

2.0.33

:released: September 3, 2024

 .. change::
     :tags: bug, sqlite
     :tickets: 11677

     Improvements to the regex used by the SQLite dialect to reflect the name
     and contents of a CHECK constraint.  Constraints with newline, tab, or
     space characters in either or both the constraint text and constraint name
     are now properly reflected.   Pull request courtesy Jeff Horemans.



 .. change::
     :tags: bug, engine
     :tickets: 11687

     Fixed issue in internal reflection cache where particular reflection
     scenarios regarding same-named quoted_name() constructs would not be
     correctly cached.  Pull request courtesy Felix Lüdin.

 .. change::
     :tags: bug, sql, regression
     :tickets: 11703

     Fixed regression in :meth:`_sql.Select.with_statement_hint` and others
     where the generative behavior of the method stopped producing a copy of the
     object.

 .. change::
     :tags: bug, mysql
     :tickets: 11731

     Fixed issue in MySQL dialect where using INSERT..FROM SELECT in combination
     with ON DUPLICATE KEY UPDATE would erroneously render on MySQL 8 and above
     the "AS new" clause, leading to syntax failures.  This clause is required
     on MySQL 8 to follow the VALUES clause if use of the "new" alias is
     present, however is not permitted to follow a FROM SELECT clause.


 .. change::
     :tags: bug, sqlite
     :tickets: 11746

     Improvements to the regex used by the SQLite dialect to reflect the name
     and contents of a UNIQUE constraint that is defined inline within a column
     definition inside of a SQLite CREATE TABLE statement, accommodating for tab
     characters present within the column / constraint line. Pull request
     courtesy John A Stevenson.




 .. change::
     :tags: bug, typing
     :tickets: 11782

     Fixed typing issue with :meth:`_sql.Select.with_only_columns`.

 .. change::
     :tags: bug, orm
     :tickets: 11788

     Correctly cleanup the internal top-level module registry when no
     inner modules or classes are registered into it.

 .. change::
     :tags: bug, schema
     :tickets: 11802

     Fixed bug where the ``metadata`` element of an ``Enum`` datatype would not
     be transferred to the new :class:`.MetaData` object when the type had been
     copied via a :meth:`.Table.to_metadata` operation, leading to inconsistent
     behaviors within create/drop sequences.

 .. change::
     :tags: bug, orm
     :tickets: 11814

     Improvements to the ORM annotated declarative type map lookup dealing with
     composed types such as ``dict[str, Any]`` linking to JSON (or others) with
     or without "future annotations" mode.



 .. change::
     :tags: change, general
     :tickets: 11818

     The pin for ``setuptools<69.3`` in ``pyproject.toml`` has been removed.
     This pin was to prevent a sudden change in setuptools to use :pep:`625`
     from taking place, which would change the file name of SQLAlchemy's source
     distribution on pypi to be an all lower case name, which is likely to cause
     problems with various build environments that expected the previous naming
     style.  However, the presence of this pin is holding back environments that
     otherwise want to use a newer setuptools, so we've decided to move forward
     with this change, with the assumption that build environments will have
     largely accommodated the setuptools change by now.



 .. change::
     :tags: bug, postgresql
     :tickets: 11821

     Revising the asyncpg ``terminate()`` fix first made in :ticket:`10717`
     which improved the resiliency of this call under all circumstances, adding
     ``asyncio.CancelledError`` to the list of exceptions that are intercepted
     as failing for a graceful ``.close()`` which will then proceed to call
     ``.terminate()``.

 .. change::
     :tags: bug, mssql
     :tickets: 11822

     Added error "The server failed to resume the transaction" to the list of
     error strings for the pymssql driver in determining a disconnect scenario,
     as observed by one user using pymssql under otherwise unknown conditions as
     leaving an unusable connection in the connection pool which fails to ping
     cleanly.

 .. change::
     :tags: bug, tests

     Added missing ``array_type`` property to the testing suite
     ``SuiteRequirements`` class.

.. changelog::

2.0.32

:released: August 5, 2024

 .. change::
     :tags: bug, examples
     :tickets: 10267

     Fixed issue in history_meta example where the "version" column in the
     versioned table needs to default to the most recent version number in the
     history table on INSERT, to suit the use case of a table where rows are
     deleted, and can then be replaced by new rows that re-use the same primary
     key identity.  This fix adds an additonal SELECT query per INSERT in the
     main table, which may be inefficient; for cases where primary keys are not
     re-used, the default function may be omitted.  Patch courtesy  Philipp H.
     v. Loewenfeld.

 .. change::
     :tags: bug, oracle
     :tickets: 11557

     Fixed table reflection on Oracle 10.2 and older where compression options
     are not supported.

 .. change::
     :tags: oracle, usecase
     :tickets: 10820

     Added API support for server-side cursors for the oracledb async dialect,
     allowing use of the :meth:`_asyncio.AsyncConnection.stream` and similar
     stream methods.

 .. change::
     :tags: bug, orm
     :tickets: 10834

     Fixed issue where using the :meth:`_orm.Query.enable_eagerloads` and
     :meth:`_orm.Query.yield_per` methods at the same time, in order to disable
     eager loading that's configured on the mapper directly, would be silently
     ignored, leading to errors or unexpected eager population of attributes.

 .. change::
     :tags: orm
     :tickets: 11163

     Added a warning noting when an
     :meth:`_engine.ConnectionEvents.engine_connect` event may be leaving
     a transaction open, which can alter the behavior of a
     :class:`_orm.Session` using such an engine as bind.
     On SQLAlchemy 2.1 :paramref:`_orm.Session.join_transaction_mode` will
     instead be ignored in all cases when the session bind is
     an :class:`_engine.Engine`.

 .. change::
     :tags: bug, general, regression
     :tickets: 11435

     Restored legacy class names removed from
     ``sqlalalchemy.orm.collections.*``, including
     :class:`_orm.MappedCollection`, :func:`_orm.mapped_collection`,
     :func:`_orm.column_mapped_collection`,
     :func:`_orm.attribute_mapped_collection`. Pull request courtesy Takashi
     Kajinami.

 .. change::
     :tags: bug, sql
     :tickets: 11471

     Follow up of :ticket:`11471` to fix caching issue where using the
     :meth:`.CompoundSelectState.add_cte` method of the
     :class:`.CompoundSelectState` construct would not set a correct cache key
     which distinguished between different CTE expressions. Also added tests
     that would detect issues similar to the one fixed in :ticket:`11544`.

 .. change::
     :tags: bug, mysql
     :tickets: 11479

     Fixed issue in MySQL dialect where ENUM values that contained percent signs
     were not properly escaped for the driver.


 .. change::
     :tags: usecase, oracle
     :tickets: 11480

     Implemented two-phase transactions for the oracledb dialect. Historically,
     this feature never worked with the cx_Oracle dialect, however recent
     improvements to the oracledb successor now allow this to be possible.  The
     two phase transaction API is available at the Core level via the
     :meth:`_engine.Connection.begin_twophase` method.

 .. change::
     :tags: bug, postgresql
     :tickets: 11522

     It is now considered a pool-invalidating disconnect event when psycopg2
     throws an "SSL SYSCALL error: Success" error message, which can occur when
     the SSL connection to Postgres is terminated abnormally.

 .. change::
     :tags: bug, schema
     :tickets: 11530

     Fixed additional issues in the event system triggered by unpickling of a
     :class:`.Enum` datatype, continuing from :ticket:`11365` and
     :ticket:`11360`,  where dynamically generated elements of the event
     structure would not be present when unpickling in a new process.

 .. change::
     :tags: bug, engine
     :tickets: 11532

     Fixed issue in "insertmanyvalues" feature where a particular call to
     ``cursor.fetchall()`` were not wrapped in SQLAlchemy's exception wrapper,
     which apparently can raise a database exception during fetch when using
     pyodbc.

 .. change::
     :tags: usecase, orm
     :tickets: 11575

     The :paramref:`_orm.aliased.name` parameter to :func:`_orm.aliased` may now
     be combined with the :paramref:`_orm.aliased.flat` parameter, producing
     per-table names based on a name-prefixed naming convention.  Pull request
     courtesy Eric Atkin.

 .. change::
     :tags: bug, postgresql
     :tickets: 11576

     Fixed issue where the :func:`_sql.collate` construct, which explicitly sets
     a collation for a given expression, would maintain collation settings for
     the underlying type object from the expression, causing SQL expressions to
     have both collations stated at once when used in further expressions for
     specific dialects that render explicit type casts, such as that of asyncpg.
     The :func:`_sql.collate` construct now assigns its own type to explicitly
     include the new collation, assuming it's a string type.

 .. change::
     :tags: bug, sql
     :tickets: 11592

     Fixed bug where the :meth:`.Operators.nulls_first()` and
     :meth:`.Operators.nulls_last()` modifiers would not be treated the same way
     as :meth:`.Operators.desc()` and :meth:`.Operators.asc()` when determining
     if an ORDER BY should be against a label name already in the statement. All
     four modifiers are now treated the same within ORDER BY.

 .. change::
     :tags: bug, orm, regression
     :tickets: 11625

     Fixed regression appearing in 2.0.21 caused by :ticket:`10279` where using
     a :func:`_sql.delete` or :func:`_sql.update` against an ORM class that is
     the base of an inheritance hierarchy, while also specifying that subclasses
     should be loaded polymorphically, would leak the polymorphic joins into the
     UPDATE or DELETE statement as well creating incorrect SQL.

 .. change::
     :tags: bug, orm, regression
     :tickets: 11661

     Fixed regression from version 1.4 in
     :meth:`_orm.Session.bulk_insert_mappings` where using the
     :paramref:`_orm.Session.bulk_insert_mappings.return_defaults` parameter
     would not populate the passed in dictionaries with newly generated primary
     key values.


 .. change::
     :tags: bug, oracle, sqlite
     :tickets: 11663

     Implemented bitwise operators for Oracle which was previously
     non-functional due to a non-standard syntax used by this database.
     Oracle's support for bitwise "or" and "xor" starts with server version 21.
     Additionally repaired the implementation of "xor" for SQLite.

     As part of this change, the dialect compliance test suite has been enhanced
     to include support for server-side bitwise tests; third party dialect
     authors should refer to new "supports_bitwise" methods in the
     requirements.py file to enable these tests.




 .. change::
     :tags: bug, typing

     Fixed internal typing issues to establish compatibility with mypy 1.11.0.
     Note that this does not include issues which have arisen with the
     deprecated mypy plugin used by SQLAlchemy 1.4-style code; see the addiional
     change note for this plugin indicating revised compatibility.

.. changelog::

2.0.31

:released: June 18, 2024

 .. change::
     :tags: usecase, reflection, mysql
     :tickets: 11285

     Added missing foreign key reflection option ``SET DEFAULT``
     in the MySQL and MariaDB dialects.
     Pull request courtesy of Quentin Roche.

 .. change::
     :tags: usecase, orm
     :tickets: 11361

     Added missing parameter :paramref:`_orm.with_polymorphic.name` that
     allows specifying the name of returned :class:`_orm.AliasedClass`.

 .. change::
     :tags: bug, orm
     :tickets: 11365

     Fixed issue where a :class:`.MetaData` collection would not be
     serializable, if an :class:`.Enum` or :class:`.Boolean` datatype were
     present which had been adapted. This specific scenario in turn could occur
     when using the :class:`.Enum` or :class:`.Boolean` within ORM Annotated
     Declarative form where type objects frequently get copied.

 .. change::
     :tags: schema, usecase
     :tickets: 11374

     Added :paramref:`_schema.Column.insert_default` as an alias of
     :paramref:`_schema.Column.default` for compatibility with
     :func:`_orm.mapped_column`.

 .. change::
     :tags: bug, general
     :tickets: 11417

     Set up full Python 3.13 support to the extent currently possible, repairing
     issues within internal language helpers as well as the serializer extension
     module.

 .. change::
     :tags: bug, sql
     :tickets: 11422

     Fixed issue when serializing an :func:`_sql.over` clause with
     unbounded range or rows.

 .. change::
     :tags: bug, sql
     :tickets: 11423

     Added missing methods :meth:`_sql.FunctionFilter.within_group`
     and :meth:`_sql.WithinGroup.filter`

 .. change::
     :tags: bug, sql
     :tickets: 11426

     Fixed bug in :meth:`_sql.FunctionFilter.filter` that would mutate
     the existing function in-place. It now behaves like the rest of the
     SQLAlchemy API, returning a new instance instead of mutating the
     original one.

 .. change::
     :tags: bug, orm
     :tickets: 11446

     Fixed issue where the :func:`_orm.selectinload` and
     :func:`_orm.subqueryload` loader options would fail to take effect when
     made against an inherited subclass that itself included a subclass-specific
     :paramref:`_orm.Mapper.with_polymorphic` setting.

 .. change::
     :tags: bug, orm
     :tickets: 11449

     Fixed very old issue involving the :paramref:`_orm.joinedload.innerjoin`
     parameter where making use of this parameter mixed into a query that also
     included joined eager loads along a self-referential or other cyclical
     relationship, along with complicating factors like inner joins added for
     secondary tables and such, would have the chance of splicing a particular
     inner join to the wrong part of the query.  Additional state has been added
     to the internal method that does this splice to make a better decision as
     to where splicing should proceed.

 .. change::
     :tags: bug, orm, regression
     :tickets: 11509

     Fixed bug in ORM Declarative where the ``__table__`` directive could not be
     declared as a class function with :func:`_orm.declared_attr` on a
     superclass, including an ``__abstract__`` class as well as coming from the
     declarative base itself.  This was a regression since 1.4 where this was
     working, and there were apparently no tests for this particular use case.

.. changelog::

2.0.30

:released: May 5, 2024

 .. change::
     :tags: bug, typing, regression
     :tickets: 11200

     Fixed typing regression caused by :ticket:`11055` in version 2.0.29 that
     added ``ParamSpec`` to the asyncio ``run_sync()`` methods, where using
     :meth:`_asyncio.AsyncConnection.run_sync` with
     :meth:`_schema.MetaData.reflect` would fail on mypy due to a mypy issue.
     Pull request courtesy of Francisco R. Del Roio.

 .. change::
     :tags: bug, engine
     :tickets: 11210

     Fixed issue in the
     :paramref:`_engine.Connection.execution_options.logging_token` option,
     where changing the value of ``logging_token`` on a connection that has
     already logged messages would not be updated to reflect the new logging
     token.  This in particular prevented the use of
     :meth:`_orm.Session.connection` to change the option on the connection,
     since the BEGIN logging message would already have been emitted.

 .. change::
     :tags: bug, orm
     :tickets: 11220

     Added new attribute :attr:`_orm.ORMExecuteState.is_from_statement` to
     detect statements created using :meth:`_sql.Select.from_statement`, and
     enhanced ``FromStatement`` to set :attr:`_orm.ORMExecuteState.is_select`,
     :attr:`_orm.ORMExecuteState.is_insert`,
     :attr:`_orm.ORMExecuteState.is_update`, and
     :attr:`_orm.ORMExecuteState.is_delete` according to the element that is
     sent to the :meth:`_sql.Select.from_statement` method itself.

 .. change::
     :tags: bug, test
     :tickets: 11268

     Ensure the ``PYTHONPATH`` variable is properly initialized when
     using ``subprocess.run`` in the tests.

 .. change::
     :tags: bug, orm
     :tickets: 11291

     Fixed issue in  :func:`_orm.selectin_polymorphic` loader option where
     attributes defined with :func:`_orm.composite` on a superclass would cause
     an internal exception on load.


 .. change::
     :tags: bug, orm, regression
     :tickets: 11292

     Fixed regression from 1.4 where using :func:`_orm.defaultload` in
     conjunction with a non-propagating loader like :func:`_orm.contains_eager`
     would nonetheless propagate the :func:`_orm.contains_eager` to a lazy load
     operation, causing incorrect queries as this option is only intended to
     come from an original load.



 .. change::
     :tags: bug, orm
     :tickets: 11305

     Fixed issue in ORM Annotated Declarative where typing issue where literals
     defined using :pep:`695` type aliases would not work with inference of
     :class:`.Enum` datatypes. Pull request courtesy of Alc-Alc.

 .. change::
     :tags: bug, engine
     :tickets: 11306

     Fixed issue in cursor handling which affected handling of duplicate
     :class:`_sql.Column` or similar objcts in the columns clause of
     :func:`_sql.select`, both in combination with arbitary :func:`_sql.text()`
     clauses in the SELECT list, as well as when attempting to retrieve
     :meth:`_engine.Result.mappings` for the object, which would lead to an
     internal error.



 .. change::
     :tags: bug, orm
     :tickets: 11327

     Fixed issue in :func:`_orm.selectin_polymorphic` loader option where the
     SELECT emitted would only accommodate for the child-most class among the
     result rows that were returned, leading intermediary-class attributes to be
     unloaded if there were no concrete instances of that intermediary-class
     present in the result.   This issue only presented itself for multi-level
     inheritance hierarchies.

 .. change::
     :tags: bug, orm
     :tickets: 11332

     Fixed issue in :meth:`_orm.Session.bulk_save_objects` where the form of the
     identity key produced when using ``return_defaults=True`` would be
     incorrect. This could lead to an errors during pickling as well as identity
     map mismatches.

 .. change::
     :tags: bug, installation
     :tickets: 11334

     Fixed an internal class that was testing for unexpected attributes to work
     correctly under upcoming Python 3.13.   Pull request courtesy Edgar
     Ramírez-Mondragón.

 ..