Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package python-alembic for openSUSE:Factory 
checked in at 2023-08-07 15:28:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-alembic (Old)
 and      /work/SRC/openSUSE:Factory/.python-alembic.new.22712 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-alembic"

Mon Aug  7 15:28:41 2023 rev:73 rq:1102506 version:1.11.1

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-alembic/python-alembic.changes    
2023-06-14 16:29:07.830391186 +0200
+++ /work/SRC/openSUSE:Factory/.python-alembic.new.22712/python-alembic.changes 
2023-08-07 15:28:42.192169686 +0200
@@ -1,0 +2,69 @@
+Sat Jul 29 21:17:43 UTC 2023 - Dirk Müller <[email protected]>
+
+- 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 <versioning_scheme>` 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.
+
+-------------------------------------------------------------------

Old:
----
  alembic-1.10.4.tar.gz

New:
----
  alembic-1.11.1.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-alembic.spec ++++++
--- /var/tmp/diff_new_pack.xkIJg2/_old  2023-08-07 15:28:43.012174778 +0200
+++ /var/tmp/diff_new_pack.xkIJg2/_new  2023-08-07 15:28:43.016174803 +0200
@@ -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

++++++ alembic-1.10.4.tar.gz -> alembic-1.11.1.tar.gz ++++++
++++ 10797 lines of diff (skipped)

Reply via email to