Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-SQLAlchemy for
openSUSE:Factory checked in at 2021-07-16 22:12:33
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2632 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy"
Fri Jul 16 22:12:33 2021 rev:86 rq:905788 version:1.4.20
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
2021-05-20 19:23:24.434356544 +0200
+++
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2632/python-SQLAlchemy.changes
2021-07-16 22:13:02.926700207 +0200
@@ -1,0 +2,377 @@
+Sun Jul 11 18:42:34 UTC 2021 - Antonio Larrosa <alarr...@suse.com>
+
+- update to version 1.4.20:
+ * orm
+ + [orm] [bug] [regression] Fixed regression in ORM regarding
+ an internal reconstitution step for the with_polymorphic()
+ construct, when the user-facing object is garbage collected
+ as the query is processed. The reconstitution was not
+ ensuring the sub-entities for the ???polymorphic??? case were
+ handled, leading to an AttributeError.
+ References: #6680
+ + [orm] [bug] [regression] Adjusted Query.union() and similar
+ set operations to be correctly compatible with the new
+ capabilities just added in #6661, with SQLAlchemy 1.4.19,
+ such that the SELECT statements rendered as elements of the
+ UNION or other set operation will include directly mapped
+ columns that are mapped as deferred; this both fixes a
+ regression involving unions with multiple levels of nesting
+ that would produce a column mismatch, and also allows the
+ undefer() option to be used at the top level of such a Query
+ without having to apply the option to each of the elements
+ within the UNION.
+ References: #6678
+ + [orm] [bug] Adjusted the check in the mapper for a callable
+ object that is used as a @validates validator function or a
+ @reconstructor reconstruction function, to check for
+ ???callable??? more liberally such as to accommodate objects
+ based on fundamental attributes like __func__ and __call___,
+ rather than testing for MethodType / FunctionType, allowing
+ things like cython functions to work properly. Pull request
+ courtesy Mi??osz Stypi??ski.
+ References: #6538
+ * engine
+ + [engine] [bug] Fixed an issue in the C extension for the Row
+ class which could lead to a memory leak in the unlikely case
+ of a Row object which referred to an ORM object that then was
+ mutated to refer back to the Row itself, creating a cycle.
+ The Python C APIs for tracking GC cycles has been added to
+ the native Row implementation to accommodate for this case.
+ References: #5348
+ + [engine] [bug] Fixed old issue where a select() made against
+ the token ???*???, which then yielded exactly one column, would
+ fail to correctly organize the cursor.description column name
+ into the keys of the result object.
+ References: #6665
+ * sql
+ + [sql] [usecase] Add a impl parameter to PickleType
+ constructor, allowing any arbitary type to be used in place
+ of the default implementation of LargeBinary. Pull request
+ courtesy jason3gb. References: #6646
+ + [sql] [bug] [orm] Fixed the class hierarchy for the Sequence
+ and the more general DefaultGenerator base, as these are
+ ???executable??? as statements they need to include Executable
+ in their hierarchy, not just StatementRole as was applied
+ arbitrarily to Sequence previously. The fix allows Sequence
+ to work in all .execute() methods including with
+ Session.execute() which was not working in the case that a
+ SessionEvents.do_orm_execute() handler was also established.
+ References: #6668
+ * schema
+ + [schema] [bug] Fixed issue where passing None for the value
+ of Table.prefixes would not store an empty list, but rather
+ the constant None, which may be unexpected by third party
+ dialects. The issue is revealed by a usage in recent versions
+ of Alembic that are passing None for this value. Pull request
+ courtesy Kai Mueller. References: #6685
+ * mysql
+ + [mysql] [usecase] Made a small adjustment in the table
+ reflection feature of the MySQL dialect to accommodate for
+ alternate MySQL-oriented databases such as TiDB which include
+ their own ???comment??? directives at the end of a constraint
+ directive within ???CREATE TABLE??? where the format doesn???t have
+ the additional space character after the comment, in this
+ case the TiDB ???clustered index??? feature. Pull request
+ courtesy Dani??l van Eeden. References: #6659
+ * misc
+ + [bug] [ext] [regression] Fixed regression in
+ sqlalchemy.ext.automap extension such that the use case of
+ creating an explicit mapped class to a table that is also the
+ relationship.secondary element of a relationship() that
+ automap will be generating would emit the ???overlaps??? warnings
+ introduced in 1.4 and discussed at relationship X will copy
+ column Q to column P, which conflicts with relationship(s):
+ ???Y???. While generating this case from automap is still subject
+ to the same caveats that the ???overlaps??? warning refers
+ towards, as automap is intended for more ad-hoc use cases,
+ the condition which produces the warning is disabled when a
+ many-to-many relationship with this particular pattern is
+ generated. References: #6679
+
+- changes from version 1.4.19:
+ * orm
+ + [orm] [bug] [regression] Fixed further regressions in the
+ same area as that of #6052 where loader options as well as
+ invocations of methods like Query.join() would fail if the
+ left side of the statement for which the option/join depends
+ upon were replaced by using the Query.with_entities() method,
+ or when using 2.0 style queries when using the
+ Select.with_only_columns() method. A new set of state has
+ been added to the objects which tracks the ???left??? entities
+ that the options / join were made against which is memoized
+ when the lead entities are changed. References: #6253, #6503
+ + [orm] [bug] Refined the behavior of ORM subquery rendering
+ with regards to deferred columns and column properties to be
+ more compatible with that of 1.3 while also providing for
+ 1.4???s newer features. As a subquery in 1.4 does not make use
+ of loader options, including undefer(), a subquery that is
+ against an ORM entity with deferred attributes will now
+ render those deferred attributes that refer directly to
+ mapped table columns, as these are needed in the outer SELECT
+ if that outer SELECT makes use of these columns; however a
+ deferred attribute that refers to a composed SQL expression
+ as we normally do with column_property() will not be part of
+ the subquery, as these can be selected explicitly if needed
+ in the subquery. If the entity is being SELECTed from this
+ subquery, the column expression can still render on ???the
+ outside??? in terms of the derived subquery columns. This
+ produces essentially the same behavior as when working with
+ 1.3. However in this case the fix has to also make sure that
+ the .selected_columns collection of an ORM-enabled select()
+ also follows these rules, which in particular allows
+ recursive CTEs to render correctly in this scenario, which
+ were previously failing to render correctly due to this
+ issue. References: #6661
+ * sql
+ + [sql] [bug] Fixed issue in CTE constructs mostly relevant to
+ ORM use cases where a recursive CTE against ???anonymous???
+ labels such as those seen in ORM column_property() mappings
+ would render in the WITH RECURSIVE xyz(...) section as their
+ raw internal label and not a cleanly anonymized name.
+ References: #6663
+ * mypy
+ + [mypy] [bug] Fixed issue in mypy plugin where class info for
+ a custom declarative base would not be handled correctly on a
+ cached mypy pass, leading to an AssertionError being raised.
+ References: #6476
+ * asyncio
+ + [asyncio] [usecase] Implemented async_scoped_session to
+ address some asyncio-related incompatibilities between
+ scoped_session and AsyncSession, in which some methods
+ (notably the async_scoped_session.remove() method) should
+ be used with the await keyword. References: #6583
+ + [asyncio] [bug] [postgresql] Fixed bug in asyncio
+ implementation where the greenlet adaptation system failed
+ to propagate BaseException subclasses, most notably including
+ asyncio.CancelledError, to the exception handling logic used
+ by the engine to invalidate and clean up the connection, thus
+ preventing connections from being correctly disposed when a
+ task was cancelled. References: #6652
+ * postgresql
+ + [postgresql] [bug] [oracle] Fixed issue where the INTERVAL
+ datatype on PostgreSQL and Oracle would produce an
+ AttributeError when used in the context of a comparison
+ operation against a timedelta() object. Pull request courtesy
+ MajorDallas. References: #6649
+ + [postgresql] [bug] Fixed issue where the pool ???pre ping???
+ feature would implicitly start a transaction, which would
+ then interfere with custom transactional flags such as
+ PostgreSQL???s ???read only??? mode when used with the psycopg2
+ driver. References: #6621
+ * mysql
+ + [mysql] [usecase] Added new construct match, which provides
+ for the full range of MySQL???s MATCH operator including
+ multiple column support and modifiers. Pull request courtesy
+ Anton Kovalevich. References: #6132
+ * mssql
+ + [mssql] [change] Made improvements to the server version
+ regexp used by the pymssql dialect to prevent a regexp
+ overflow in case of an invalid version string.
+ References: #6253, #6503
+ + [mssql] [bug] Fixed bug where the ???schema_translate_map???
+ feature would fail to function correctly in conjunction with
+ an INSERT into a table that has an IDENTITY column, where the
+ value of the IDENTITY column were specified in the values of
+ the INSERT thus triggering SQLAlchemy???s feature of setting
+ IDENTITY INSERT to ???on???; it???s in this directive where the
+ schema translate map would fail to be honored.
+ References: #6658
+
+- changes from version 1.4.18:
+ * orm
+ + [orm] [performance] [bug] [regression] Fixed regression
+ involving how the ORM would resolve a given mapped column to
+ a result row, where under cases such as joined eager loading,
+ a slightly more expensive ???fallback??? could take place to set
+ up this resolution due to some logic that was removed since
+ 1.3. The issue could also cause deprecation warnings
+ involving column resolution to be emitted when using a 1.4
+ style query with joined eager loading. References: #6596
+ + [orm] [bug] Clarified the current purpose of the
+ relationship.bake_queries flag, which in 1.4 is to enable or
+ disable ???lambda caching??? of statements within the ???lazyload???
+ and ???selectinload??? loader strategies; this is separate from
+ the more foundational SQL query cache that is used for most
+ statements. Additionally, the lazy loader no longer uses its
+ own cache for many-to-one SQL queries, which was an
+ implementation quirk that doesn???t exist for any other loader
++++ 180 more lines (skipped)
++++ between
/work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
++++ and
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2632/python-SQLAlchemy.changes
Old:
----
SQLAlchemy-1.4.15.tar.gz
tests_overcome_bpo42967.patch
New:
----
SQLAlchemy-1.4.20.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.TEIXfz/_old 2021-07-16 22:13:03.654695063 +0200
+++ /var/tmp/diff_new_pack.TEIXfz/_new 2021-07-16 22:13:03.658695035 +0200
@@ -20,17 +20,13 @@
%define skip_python2 1
%define oldpython python
Name: python-SQLAlchemy
-Version: 1.4.15
+Version: 1.4.20
Release: 0
Summary: Database Abstraction Library
License: MIT
URL: https://www.sqlalchemy.org
Source:
https://files.pythonhosted.org/packages/source/S/SQLAlchemy/SQLAlchemy-%{version}.tar.gz
Source1: SQLAlchemy.keyring
-# PATCH-FIX-UPSTREAM tests_overcome_bpo42967.patch
gh#sqlalchemy/sqlalchemy#5969 mc...@suse.com
-# over effects of bpo#42967, which forbade mixing amps and
-# semicolons in query strings as separators.
-Patch0: tests_overcome_bpo42967.patch
# devel is needed for optional C extensions cprocessors.so, cresultproxy.so
and cutils.so
BuildRequires: %{python_module devel}
BuildRequires: %{python_module setuptools}
++++++ SQLAlchemy-1.4.15.tar.gz -> SQLAlchemy-1.4.20.tar.gz ++++++
/work/SRC/openSUSE:Factory/python-SQLAlchemy/SQLAlchemy-1.4.15.tar.gz
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2632/SQLAlchemy-1.4.20.tar.gz
differ: char 5, line 1
