From 8e2cbab40b6915bfecf5cdd0d05e259b72b8d0b74d55d57a6d785223cbdbcc09 Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Sat, 29 Jul 2023 21:25:10 +0000 Subject: [PATCH] - update to 1.11.1: * As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been `clarified ` in the documentation), * :ticket:`1130` modified calling signatures for most operations to consider all optional keyword parameters to be keyword-only arguments, to match what was always documented and generated by autogenerate. However, two of these changes were identified as possibly problematic without a more formal deprecation warning being emitted which were the ``table_name`` parameter to :meth:`.Operations.drop_index`, which was generated positionally by autogenerate prior to version 0.6.3 released in 2014, and ``type_`` in :meth:`.Operations.drop_constraint` and :meth:`.BatchOperations.drop_constraint`, which was documented positionally in one example in the batch documentation. * Fixed typing use of :class:`~sqlalchemy.schema.Column` and other generic SQLAlchemy classes. * Restored the output type of :meth:`.Config.get_section` to include ``Dict[str, str]`` as a potential return type, which had been changed to immutable ``Mapping[str, str]``. When a section is returned and the default is not used, a mutable dictionary is returned. * Added placeholder classes for :class:`~.sqla.Computed` and * :class:`~.sqla.Identity` when older 1.x SQLAlchemy versions are in use, namely prior to SQLAlchemy 1.3.11 when the :class:`~.sqla.Computed` construct was introduced. Previously these were set to None, however this could cause issues with certain codepaths that were using ``isinstance()`` such as one within "batch mode". OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-alembic?expand=0&rev=146 --- alembic-1.10.4.tar.gz | 3 -- alembic-1.11.1.tar.gz | 3 ++ python-alembic.changes | 69 ++++++++++++++++++++++++++++++++++++++++++ python-alembic.spec | 2 +- 4 files changed, 73 insertions(+), 4 deletions(-) delete mode 100644 alembic-1.10.4.tar.gz create mode 100644 alembic-1.11.1.tar.gz diff --git a/alembic-1.10.4.tar.gz b/alembic-1.10.4.tar.gz deleted file mode 100644 index bda1638..0000000 --- a/alembic-1.10.4.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:295b54bbb92c4008ab6a7dcd1e227e668416d6f84b98b3c4446a2bc6214a556b -size 1152769 diff --git a/alembic-1.11.1.tar.gz b/alembic-1.11.1.tar.gz new file mode 100644 index 0000000..683de04 --- /dev/null +++ b/alembic-1.11.1.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a810a6b012c88b33458fceb869aef09ac75d6ace5291915ba7fae44de372c01 +size 1176522 diff --git a/python-alembic.changes b/python-alembic.changes index 8d2ed38..85d9098 100644 --- a/python-alembic.changes +++ b/python-alembic.changes @@ -1,3 +1,72 @@ +------------------------------------------------------------------- +Sat Jul 29 21:17:43 UTC 2023 - Dirk Müller + +- update to 1.11.1: + * As Alembic 1.11.0 is considered a major release (Alembic does + not use semver, nor does its parent project SQLAlchemy; + this has been `clarified ` in the documentation), + * :ticket:`1130` modified calling signatures for most + operations to consider all optional keyword parameters to + be keyword-only arguments, to match what was always documented + and generated by autogenerate. However, two of these + changes were identified as possibly problematic without a + more formal deprecation warning being emitted which were the + ``table_name`` parameter to :meth:`.Operations.drop_index`, + which was generated positionally by autogenerate prior to + version 0.6.3 released in 2014, and + ``type_`` in :meth:`.Operations.drop_constraint` and + :meth:`.BatchOperations.drop_constraint`, which was + documented positionally in one example in the batch documentation. + * Fixed typing use of :class:`~sqlalchemy.schema.Column` and + other generic SQLAlchemy classes. + * Restored the output type of :meth:`.Config.get_section` to + include ``Dict[str, str]`` as a potential return type, which + had been changed to immutable ``Mapping[str, str]``. + When a section is returned and the default is not used, + a mutable dictionary is returned. + * Added placeholder classes for :class:`~.sqla.Computed` and + * :class:`~.sqla.Identity` when older 1.x SQLAlchemy versions + are in use, namely prior to SQLAlchemy 1.3.11 when the + :class:`~.sqla.Computed` construct was introduced. + Previously these were set to None, however this + could cause issues with certain codepaths that were using + ``isinstance()`` such as one within "batch mode". + * Correctly pass previously ignored arguments ``insert_before`` + and ``insert_after`` in ``batch_alter_column`` + * Argument signatures of Alembic operations now enforce + keyword-only arguments as passed as keyword and not + positionally, such as Operations.create_table.schema + .Operations.add_column.type_, etc. + * Fix autogenerate issue with PostgreSQL + :class:`.ExcludeConstraint` that included sqlalchemy + functions. The function text was previously rendered + as a plain string without surrounding with ``text()``. + * Fixed regression caused by :ticket:`1166` released in version + 1.10.0 which caused MySQL unique constraints with multiple + columns to not compare correctly within autogenerate, + due to different sorting rules on unique constraints vs. + indexes, which in MySQL are shared constructs. + * Repaired the return signatures for :class:`.Operations` that + mostly return ``None``, and were erroneously referring to + ``Optional[Table]`` in many cases. + * Modified the autogenerate implementation for comparing + "server default" values from user-defined metadata to not + apply any quoting to the value before comparing it to the + server-reported default, except for within dialect-specific + routines as needed. This change will affect the format of + the server default as passed to the + :paramref:`.EnvironmentContext.configure.compare_server_defau + lt` hook, as well as for third party dialects that implement + a custom ``compare_server_default`` hook in their alembic + impl, to be passed "as is" and not including additional + quoting. Custom implementations which rely on this quoting + should adjust their approach based on observed formatting. + * allow running async functions in the ``upgrade`` or + ``downgrade`` migration function when running alembic using + an async dialect. This function will receive as first argument + an :class:`~sqlalchemy.ext.asyncio.AsyncConnection` sharing the + transaction used in the migration context. + ------------------------------------------------------------------- Tue Jun 13 11:35:16 UTC 2023 - Dirk Müller diff --git a/python-alembic.spec b/python-alembic.spec index ab9a56c..345337c 100644 --- a/python-alembic.spec +++ b/python-alembic.spec @@ -18,7 +18,7 @@ %{?sle15_python_module_pythons} Name: python-alembic -Version: 1.10.4 +Version: 1.11.1 Release: 0 Summary: A database migration tool for SQLAlchemy License: MIT