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 2023-05-30 22:02:06
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1533 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy"
Tue May 30 22:02:06 2023 rev:107 rq:1089853 version:2.0.15
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
2023-05-13 17:17:31.130338849 +0200
+++
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1533/python-SQLAlchemy.changes
2023-05-30 22:02:19.978971599 +0200
@@ -1,0 +2,109 @@
+Tue May 30 15:57:30 UTC 2023 - Daniel Garcia <daniel.gar...@suse.com>
+
+- Switch documentation to be within the main package.
+
+-------------------------------------------------------------------
+Sat May 20 10:32:50 UTC 2023 - Ben Greiner <c...@bnavigator.de>
+
+- Update to 2.0.15
+ # orm
+ * As more projects are using new-style â2.0â ORM querying, itâs
+ becoming apparent that the conditional nature of âautoflushâ,
+ being based on whether or not the given statement refers to ORM
+ entities, is becoming more of a key behavior. Up until now, the
+ âORMâ flag for a statement has been loosely based around
+ whether or not the statement returns rows that correspond to
+ ORM entities or columns; the original purpose of the âORMâ flag
+ was to enable ORM-entity fetching rules which apply
+ post-processing to Core result sets as well as ORM loader
+ strategies to the statement. For statements that donât build on
+ rows that contain ORM entities, the âORMâ flag was considered
+ to be mostly unnecessary.
+ * It still may be the case that âautoflushâ would be better
+ taking effect for all usage of Session.execute() and related
+ methods, even for purely Core SQL constructs. However, this
+ still could impact legacy cases where this is not expected and
+ may be more of a 2.1 thing. For now however, the rules for the
+ âORM-flagâ have been opened up so that a statement that
+ includes ORM entities or attributes anywhere within, including
+ in the WHERE / ORDER BY / GROUP BY clause alone, within scalar
+ subqueries, etc. will enable this flag. This will cause
+ âautoflushâ to occur for such statements and also be visible
+ via the ORMExecuteState.is_orm_statement event-level attribute.
+ References: #9805
+ # postgresql
+ * Repaired the base Uuid datatype for the PostgreSQL dialect to
+ make full use of the PG-specific UUID dialect-specific datatype
+ when ânative_uuidâ is selected, so that PG driver behaviors are
+ included. This issue became apparent due to the
+ insertmanyvalues improvement made as part of #9618, where in a
+ similar manner as that of #9739, the asyncpg driver is very
+ sensitive to datatype casts being present or not, and the
+ PostgreSQL driver-specific native UUID datatype must be invoked
+ when this generic type is used so that these casts take place.
+ References: #9808
+- Release 2.0.13
+ # orm
+ * Modified the JoinedLoader implementation to use a simpler
+ approach in one particular area where it previously used a
+ cached structure that would be shared among threads. The
+ rationale is to avoid a potential race condition which is
+ suspected of being the cause of a particular crash thatâs been
+ reported multiple times. The cached structure in question is
+ still ultimately âcachedâ via the compiled SQL cache, so a
+ performance degradation is not anticipated.
+ References: #9777
+ * Fixed regression where use of update() or delete() within a CTE
+ construct, then used in a select(), would raise a CompileError
+ as a result of ORM related rules for performing ORM-level
+ update/delete statements.
+ References: #9767
+ * Fixed issue in new ORM Annotated Declarative where using a
+ ForeignKey (or other column-level constraint) inside of
+ mapped_column() which is then copied out to models via pep-593
+ Annotated would apply duplicates of each constraint to the
+ Column as produced in the target Table, leading to incorrect
+ CREATE TABLE DDL as well as migration directives under Alembic.
+ References: #9766
+ * Fixed issue where using additional relationship criteria with
+ the joinedload() loader option, where the additional criteria
+ itself contained correlated subqueries that referred to the
+ joined entities and therefore also required âadaptionâ to
+ aliased entities, would be excluded from this adaption,
+ producing the wrong ON clause for the joinedload.
+ References: #9779
+ # sql
+ * Generalized the MSSQL try_cast() function into the sqlalchemy.
+ import namespace so that it may be implemented by third party
+ dialects as well. Within SQLAlchemy, the try_cast() function
+ remains a SQL Server-only construct that will raise
+ CompileError if used with backends that donât support it.
+ * try_cast() implements a CAST where un-castable conversions are
+ returned as NULL, instead of raising an error. Theoretically,
+ the construct could be implemented by third party dialects for
+ Google BigQuery, DuckDB, and Snowflake, and possibly others.
+ Pull request courtesy Nick Crews.
+ References: #9752
+ * Fixed issue in values() construct where an internal compilation
+ error would occur if the construct were used inside of a scalar
+ subquery.
+ References: #9772
+ # postgresql
+ * Fixed apparently very old issue where the ENUM.create_type
+ parameter, when set to its non-default of False, would not be
+ propagated when the Column which itâs a part of were copied, as
+ is common when using ORM Declarative mixins. References: #9773
+ # tests
+ * Fixed test that relied on the sys.getsizeof() function to not
+ run on pypy, where this function appears to have different
+ behavior than it does on cpython. References: #9789
+- PEP517
+- Add missing runtime requirement
+
+-------------------------------------------------------------------
+Sun May 14 16:30:22 UTC 2023 - Dirk Müller <dmuel...@suse.com>
+
+- update to 2.0.13:
+ *
https://docs.sqlalchemy.org/en/20/changelog/changelog_20.html#change-2.0.13
+
+-------------------------------------------------------------------
Old:
----
SQLAlchemy-2.0.12.tar.gz
New:
----
SQLAlchemy-2.0.15.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.DZ2MOs/_old 2023-05-30 22:02:20.462974452 +0200
+++ /var/tmp/diff_new_pack.DZ2MOs/_new 2023-05-30 22:02:20.466974475 +0200
@@ -16,11 +16,9 @@
#
-%define skip_python2 1
-%define oldpython python
%{?sle15_python_module_pythons}
Name: python-SQLAlchemy
-Version: 2.0.12
+Version: 2.0.15
Release: 0
Summary: Database Abstraction Library
License: MIT
@@ -29,13 +27,16 @@
Source1: SQLAlchemy.keyring
# devel is needed for optional C extensions cprocessors.so, cresultproxy.so
and cutils.so
BuildRequires: %{python_module Cython3}
-BuildRequires: %{python_module devel}
+BuildRequires: %{python_module devel >= 3.7}
+BuildRequires: %{python_module pip}
BuildRequires: %{python_module setuptools}
+BuildRequires: %{python_module wheel}
BuildRequires: %{pythons}
BuildRequires: fdupes
BuildRequires: python-rpm-macros
Requires: python
-Requires: python-greenlet
+Requires: python-greenlet > 0.4.17
+Requires: python-typing_extensions >= 4.2.0
Provides: python-sqlalchemy = %{version}
Obsoletes: python-sqlalchemy < %{version}
Conflicts: python-SQLAlchemy1
@@ -77,10 +78,10 @@
%build
export CFLAGS="%{optflags} -fno-strict-aliasing"
-%python_build
+%pyproject_wheel
%install
-%python_install
+%pyproject_install
%python_expand %fdupes %{buildroot}%{$python_sitearch}
%check
@@ -90,9 +91,11 @@
%license LICENSE
%doc CHANGES.rst README.rst README.dialects.rst README.unittests.rst
%{python_sitearch}/sqlalchemy/
-%{python_sitearch}/SQLAlchemy-%{version}-py*.egg-info
+%{python_sitearch}/SQLAlchemy-%{version}.dist-info
+%if 0%{?suse_version} > 1500
%files -n %{name}-doc
+%endif
%doc doc/
%doc examples/
++++++ SQLAlchemy-2.0.12.tar.gz -> SQLAlchemy-2.0.15.tar.gz ++++++
/work/SRC/openSUSE:Factory/python-SQLAlchemy/SQLAlchemy-2.0.12.tar.gz
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1533/SQLAlchemy-2.0.15.tar.gz
differ: char 5, line 1
