From 0f77bf10acf108578335089bfb387fe8cb69ed99 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Wed, 14 May 2025 08:20:03 -0400 Subject: [PATCH] changelog edits Change-Id: Ib2bb33698f58a62c945d147c39d3ac6af908b802 (cherry picked from commit c7d5c2ab5a7c5c97f80a904fcd3d5dcc9ebe954d) --- doc/build/changelog/unreleased_20/12405.rst | 16 +++++++++------- doc/build/changelog/unreleased_20/12488.rst | 6 +++--- doc/build/changelog/unreleased_20/12566.rst | 6 +++--- 3 files changed, 15 insertions(+), 13 deletions(-) diff --git a/doc/build/changelog/unreleased_20/12405.rst b/doc/build/changelog/unreleased_20/12405.rst index f90546ad5a..f05d714bba 100644 --- a/doc/build/changelog/unreleased_20/12405.rst +++ b/doc/build/changelog/unreleased_20/12405.rst @@ -1,10 +1,12 @@ .. change:: - :tags: bug, orm + :tags: bug, platform :tickets: 12405 - Changes to the test suite to accommodate Python 3.14 and its new - implementation of :pep:`649`, which highly modifies how typing annotations - are interpreted at runtime. Use of the new - ``annotationlib.get_annotations()`` function is enabled when python 3.14 is - present, and many other changes to how pep-484 type objects are interpreted - at runtime are made. + Adjusted the test suite as well as the ORM's method of scanning classes for + annotations to work under current beta releases of Python 3.14 (currently + 3.14.0b1) as part of an ongoing effort to support the production release of + this Python release. Further changes to Python's means of working with + annotations is expected in subsequent beta releases for which SQLAlchemy's + test suite will need further adjustments. + + diff --git a/doc/build/changelog/unreleased_20/12488.rst b/doc/build/changelog/unreleased_20/12488.rst index d81d025bdd..55c6e7b655 100644 --- a/doc/build/changelog/unreleased_20/12488.rst +++ b/doc/build/changelog/unreleased_20/12488.rst @@ -2,7 +2,7 @@ :tags: bug, mysql :tickets: 12488 - Fixed regression caused by the DEFAULT rendering changes in 2.0.40 - :ticket:`12425` where using lowercase `on update` in a MySQL server default - would incorrectly apply parenthesis, leading to errors when MySQL + Fixed regression caused by the DEFAULT rendering changes in version 2.0.40 + via :ticket:`12425` where using lowercase ``on update`` in a MySQL server + default would incorrectly apply parenthesis, leading to errors when MySQL interpreted the rendered DDL. Pull request courtesy Alexander Ruehe. diff --git a/doc/build/changelog/unreleased_20/12566.rst b/doc/build/changelog/unreleased_20/12566.rst index 194936f967..42d5eed175 100644 --- a/doc/build/changelog/unreleased_20/12566.rst +++ b/doc/build/changelog/unreleased_20/12566.rst @@ -2,6 +2,6 @@ :tags: bug, sqlite :tickets: 12566 - Fixed and added test support for a few SQLite SQL functions hardcoded into - the compiler most notably the "localtimestamp" function which rendered with - incorrect internal quoting. + Fixed and added test support for some SQLite SQL functions hardcoded into + the compiler, most notably the ``localtimestamp`` function which rendered + with incorrect internal quoting. -- 2.47.2