Hello community, here is the log from the commit of package python-SQLAlchemy for openSUSE:Factory checked in at 2019-04-15 11:50:17 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old) and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.17052 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy" Mon Apr 15 11:50:17 2019 rev:62 rq:693001 version:1.3.2 Changes: -------- --- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes 2019-03-12 09:46:14.571623840 +0100 +++ /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.17052/python-SQLAlchemy.changes 2019-04-15 11:50:19.350482519 +0200 @@ -1,0 +2,61 @@ +Wed Apr 10 15:37:48 UTC 2019 - Arun Persaud <[email protected]> + +- update to version 1.3.2: + * orm + + [orm] [bug] [ext] Restored instance-level support for plain + Python descriptors, e.g. @property objects, in conjunction with + association proxies, in that if the proxied object is not within + ORM scope at all, it gets classified as “ambiguous” but is + proxed directly. For class level access, a basic class + level"__get__()" now returns the + AmbiguousAssociationProxyInstance directly, rather than raising + its exception, which is the closest approximation to the + previous behavior that returned the AssociationProxy itself + that’s possible. Also improved the stringification of these + objects to be more descriptive of current state. References: + #4573, #4574 + + [orm] [bug] Fixed bug where use of with_polymorphic() or other + aliased construct would not properly adapt when the aliased + target were used as the Select.correlate_except() target of a + subquery used inside of a column_property(). This required a fix + to the clause adaption mechanics to properly handle a selectable + that shows up in the “correlate except” list, in a similar + manner as which occurs for selectables that show up in the + “correlate” list. This is ultimately a fairly fundamental bug + that has lasted for a long time but it is hard to come across + it. References: #4537 + + [orm] [bug] Fixed regression where a new error message that was + supposed to raise when attempting to link a relationship option + to an AliasedClass without using PropComparator.of_type() would + instead raise an AttributeError. Note that in 1.3, it is no + longer valid to create an option path from a plain mapper + relationship to an AliasedClass without using + PropComparator.of_type(). References: #4566 + * sql + + [sql] [bug] [documentation] Thanks to TypeEngine methods + bind_expression, column_expression work with Variant, + type-specific types, we no longer need to rely on recipes that + subclass dialect-specific types directly, TypeDecorator can now + handle all cases. Additionally, the above change made it + slightly less likely that a direct subclass of a base SQLAlchemy + type would work as expected, which could be + misleading. Documentation has been updated to use TypeDecorator + for these examples including the PostgreSQL “ArrayOfEnum” + example datatype and direct support for the “subclass a type + directly” has been removed. References: #4580 + * postgresql + + [postgresql] [feature] Added support for parameter-less + connection URLs for the psycopg2 dialect, meaning, the URL can + be passed to create_engine() as "postgresql+psycopg2://" with no + additional arguments to indicate an empty DSN passed to libpq, + which indicates to connect to “localhost” with no username, + password, or database given. Pull request courtesy Julian + Mehnle. References: #4562 + + [postgresql] [bug] Modified the Select.with_for_update.of + parameter so that if a join or other composed selectable is + passed, the individual Table objects will be filtered from it, + allowing one to pass a join() object to the parameter, as occurs + normally when using joined table inheritance with the ORM. Pull + request courtesy Raymond Lu. References: #4550 + +------------------------------------------------------------------- Old: ---- SQLAlchemy-1.3.1.tar.gz New: ---- SQLAlchemy-1.3.2.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-SQLAlchemy.spec ++++++ --- /var/tmp/diff_new_pack.N4qbhK/_old 2019-04-15 11:50:20.898483339 +0200 +++ /var/tmp/diff_new_pack.N4qbhK/_new 2019-04-15 11:50:20.938483360 +0200 @@ -19,7 +19,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} %define oldpython python Name: python-SQLAlchemy -Version: 1.3.1 +Version: 1.3.2 Release: 0 Summary: Database Abstraction Library License: MIT @@ -77,7 +77,7 @@ %python_expand %fdupes %{buildroot}%{$python_sitearch} %check -%python_expand py.test-%{$python_bin_suffix} -v +%pytest %files %{python_files} %license LICENSE ++++++ SQLAlchemy-1.3.1.tar.gz -> SQLAlchemy-1.3.2.tar.gz ++++++ ++++ 124906 lines of diff (skipped)
