Hello community,

here is the log from the commit of package python-SQLAlchemy for 
openSUSE:Factory checked in at 2020-03-27 00:28:02
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
 and      /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.3160 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-SQLAlchemy"

Fri Mar 27 00:28:02 2020 rev:74 rq:787144 version:1.3.15

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes      
2020-01-30 09:34:32.681269959 +0100
+++ 
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.3160/python-SQLAlchemy.changes
    2020-03-27 00:28:03.372340651 +0100
@@ -1,0 +2,29 @@
+Sat Mar 14 12:26:48 UTC 2020 - Dirk Mueller <dmuel...@suse.com>
+
+- update to 1.3.15:
+  * Adjusted the error message emitted by :meth:`.Query.join` when a left hand
+    side can't be located that the :meth:`.Query.select_from` method is the
+    best way to resolve the issue.  Also, within the 1.3 series, used a
+    deterministic ordering when determining the FROM clause from a given column
+    entity passed to :class:`.Query` so that the same expression is determined
+    each time.
+  * Fixed regression in 1.3.14 due to :ticket:`4849` where a sys.exc_info()
+    call failed to be invoked correctly when a flush error would occur. Test
+    coverage has been added for this exception case.
+  * Fixed bug where a CTE of an INSERT/UPDATE/DELETE that also uses RETURNING
+    could then not be SELECTed from directly, as the internal state of the
+    compiler would try to treat the outer SELECT as a DELETE statement itself
+    and access nonexistent state.
+  * Fixed regression caused in 1.3.13 by :ticket:`5056` where a refactor of the
+    ORM path registry system made it such that a path could no longer be
+    compared to an empty tuple, which can occur in a particular kind of joined
+    eager loading path.   The "empty tuple" use case has been resolved so that
+    the path registry is compared to a path registry in all cases; 
+- Fix build for older distributions by buildrequiring a new-enough pytest
+
+-------------------------------------------------------------------
+Thu Mar 12 07:37:00 UTC 2020 - Tomáš Chvátal <tchva...@suse.com>
+
+- Fix build without python2
+
+-------------------------------------------------------------------

Old:
----
  SQLAlchemy-1.3.13.tar.gz

New:
----
  SQLAlchemy-1.3.15.tar.gz

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

Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.AU0Y26/_old  2020-03-27 00:28:04.656341301 +0100
+++ /var/tmp/diff_new_pack.AU0Y26/_new  2020-03-27 00:28:04.656341301 +0100
@@ -19,7 +19,7 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define oldpython python
 Name:           python-SQLAlchemy
-Version:        1.3.13
+Version:        1.3.15
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT
@@ -36,8 +36,8 @@
 Obsoletes:      python-sqlalchemy < %{version}
 # SECTION test requirements
 BuildRequires:  %{python_module mock}
+BuildRequires:  %{python_module pytest >= 4.4.0}
 BuildRequires:  %{python_module pytest-xdist}
-BuildRequires:  %{python_module pytest}
 # /SECTION
 %ifpython2
 Obsoletes:      %{oldpython}-sqlalchemy < %{version}
@@ -83,7 +83,7 @@
 %license LICENSE
 %doc CHANGES README.rst README.dialects.rst README.unittests.rst
 %{python_sitearch}/sqlalchemy/
-%{python_sitearch}/SQLAlchemy-%{version}-py%{py_ver}.egg-info
+%{python_sitearch}/SQLAlchemy-%{version}-py*.egg-info
 
 %files -n %{name}-doc
 %doc doc/

++++++ SQLAlchemy-1.3.13.tar.gz -> SQLAlchemy-1.3.15.tar.gz ++++++
++++ 20126 lines of diff (skipped)


Reply via email to