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 2021-10-20 20:23:44 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-alembic (Old) and /work/SRC/openSUSE:Factory/.python-alembic.new.1890 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-alembic" Wed Oct 20 20:23:44 2021 rev:60 rq:925915 version:1.7.4 Changes: -------- --- /work/SRC/openSUSE:Factory/python-alembic/python-alembic.changes 2021-06-06 22:41:05.319446359 +0200 +++ /work/SRC/openSUSE:Factory/.python-alembic.new.1890/python-alembic.changes 2021-10-20 20:24:31.649387083 +0200 @@ -1,0 +2,103 @@ +Sun Oct 17 22:28:50 UTC 2021 - Dirk M??ller <dmuel...@suse.com> + +- update to 1.7.4: + * Fixed a regression that prevented the use of post write hooks on python + version lower than 3.9 + * Added missing attributes from context stubs. + * Fixed issue where registration of custom ops was prone to failure due to + the registration process running exec() on generated code that as of the + 1.7 series includes pep-484 annotations, which in the case of end user code + would result in name resolution errors when the exec occurs + +------------------------------------------------------------------- +Sun Sep 5 16:08:27 UTC 2021 - Arun Persaud <a...@gmx.de> + +- specfile: + * skip python 2 builds + * require importlib-resources + +- update to version 1.7.1: + * Corrected "universal wheel" directive in setup.cfg so that + building a wheel does not target Python 2. The PyPi files index + for 1.7.0 was corrected manually. Pull request courtesy layday. + * Fixed issue in generated .pyi files where default values for + "Optional" arguments were missing, thereby causing mypy to + consider them as required. + * Fixed regression in batch mode due to :ticket:`883` where the + "auto" mode of batch would fail to accommodate any additional + migration directives beyond encountering an "add_column()" + directive, due to a mis-application of the conditional logic that + was added as part of this change, leading to "recreate" mode not + being used in cases where it is required for SQLite such as for + unique constraints. + +- changes from version 1.7.0: + * Fixed regression due to :ticket:`803` where the ".info" and + ".comment" attributes of "Table" would be lost inside of the + :class:`.DropTableOp` class, which when "reversed" into a + :class:`.CreateTableOp` would then have lost these elements. Pull + request courtesy Nicolas CANIART. + * Enhance "version_locations" parsing to handle paths containing + spaces. The new configuration option "version_path_separator" + specifies the character to use when splitting the + "version_locations" string. The default for new configurations is + "version_path_separator = os", which will use "os.pathsep" (e.g., + ";" on Windows). + * Alembic 1.7 now supports Python 3.6 and above; support for prior + versions including Python 2.7 has been dropped. + * Batch "auto" mode will now select for "recreate" if the + "add_column()" operation is used on SQLite, and the column itself + meets the criteria for SQLite where ADD COLUMN is not allowed, in + this case a functional or parenthesized SQL expression or a + "Computed" (i.e. generated) column. + * Make the "python-dateutil" library an optional dependency. This + library is only required if the "timezone" option is used in the + Alembic configuration. An extra require named "tz" is available + with "pip install alembic[tz]" to install it. + * Re-implemented the "python-editor" dependency as a small internal + function to avoid the need for external dependencies. + * Named CHECK constraints are now supported by batch mode, and will + automatically be part of the recreated table assuming they are + named. They also can be explicitly dropped using + "op.drop_constraint()". For "unnamed" CHECK constraints, these are + still skipped as they cannot be distinguished from the CHECK + constraints that are generated by the "Boolean" and "Enum" + datatypes. Note that this change may require adjustments to + migrations that drop or rename columns which feature an associated + named check constraint, such that an additional + "op.drop_constraint()" directive should be added for that named + constraint as there will no longer be an associated column for it; + for the "Boolean" and "Enum" datatypes, an "existing_type" keyword + may be passed to "BatchOperations.drop_constraint" as well. + * The dependency on "pkg_resources" which is part of "setuptools" + has been removed, so there is no longer any runtime dependency on + "setuptools". The functionality has been replaced with + "importlib.metadata" and "importlib.resources" which are both part + of Python std.lib, or via pypy dependency "importlib-metadata" for + Python version < 3.8 and "importlib-resources" for Python version + < 3.9 (while importlib.resources was added to Python in 3.7, it + did not include the "files" API until 3.9). + * Created a "test suite" similar to the one for SQLAlchemy, allowing + developers of third-party dialects to test their code against a + set of Alembic tests that have been specially selected to exercise + back-end database operations. At the time of release, third-party + dialects that have adopted the Alembic test suite to verify + compatibility include `CockroachDB + <https://pypi.org/project/sqlalchemy-cockroachdb/>`_ and `SAP ASE + (Sybase) <https://pypi.org/project/sqlalchemy-sybase/>`_. + * Fixed issue where usage of the PostgreSQL "postgresql_include" + option within a :meth:`.Operations.create_index` would raise a + KeyError, as the additional column(s) need to be added to the + table object used by the construct internally. The issue is + equivalent to the SQL Server issue fixed in :ticket:`513`. Pull + request courtesy Steven Bronson. + * pep-484 type annotations have been added throughout the library. + Additionally, stub .pyi files have been added for the + "dynamically" generated Alembic modules "alembic.op" and + "alembic.config", which include complete function signatures and + docstrings, so that the functions in these namespaces will have + both IDE support (vscode, pycharm, etc) as well as support for + typing tools like Mypy. The files themselves are statically + generated from their source functions within the source tree. + +------------------------------------------------------------------- Old: ---- alembic-1.6.5.tar.gz New: ---- alembic-1.7.4.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-alembic.spec ++++++ --- /var/tmp/diff_new_pack.OottRz/_old 2021-10-20 20:24:32.221387436 +0200 +++ /var/tmp/diff_new_pack.OottRz/_new 2021-10-20 20:24:32.221387436 +0200 @@ -17,8 +17,9 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} +%define skip_python2 1 Name: python-alembic -Version: 1.6.5 +Version: 1.7.4 Release: 0 Summary: A database migration tool for SQLAlchemy License: MIT @@ -27,6 +28,7 @@ Source1: python-alembic-rpmlintrc BuildRequires: %{python_module Mako} BuildRequires: %{python_module SQLAlchemy >= 1.3.0} +BuildRequires: %{python_module importlib-resources} BuildRequires: %{python_module mock} BuildRequires: %{python_module pytest} BuildRequires: %{python_module python-dateutil} @@ -37,6 +39,7 @@ BuildRequires: python-rpm-macros Requires: python-Mako Requires: python-SQLAlchemy >= 1.3.0 +Requires: python-importlib-resources Requires: python-python-dateutil Requires: python-python-editor >= 0.3 Requires(post): update-alternatives ++++++ alembic-1.6.5.tar.gz -> alembic-1.7.4.tar.gz ++++++ ++++ 28855 lines of diff (skipped)
