Accepting request 692969 from home:apersaud:branches:devel:languages:python
update to latest version OBS-URL: https://build.opensuse.org/request/show/692969 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-SQLAlchemy?expand=0&rev=137
This commit is contained in:
committed by
Git OBS Bridge
parent
c7d6061eb0
commit
0bda990950
@@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:781fb7b9d194ed3fc596b8f0dd4623ff160e3e825dd8c15472376a438c19598b
|
||||
size 5864223
|
||||
3
SQLAlchemy-1.3.2.tar.gz
Normal file
3
SQLAlchemy-1.3.2.tar.gz
Normal file
@@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d5432832f91d200c3d8b473a266d59442d825f9ea744c467e68c5d9a9479fbce
|
||||
size 5851340
|
||||
@@ -1,3 +1,64 @@
|
||||
-------------------------------------------------------------------
|
||||
Wed Apr 10 15:37:48 UTC 2019 - Arun Persaud <arun@gmx.de>
|
||||
|
||||
- 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
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Sun Mar 10 16:34:50 UTC 2019 - Arun Persaud <arun@gmx.de>
|
||||
|
||||
|
||||
@@ -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 @@ export CFLAGS="%{optflags} -fno-strict-aliasing"
|
||||
%python_expand %fdupes %{buildroot}%{$python_sitearch}
|
||||
|
||||
%check
|
||||
%python_expand py.test-%{$python_bin_suffix} -v
|
||||
%pytest
|
||||
|
||||
%files %{python_files}
|
||||
%license LICENSE
|
||||
|
||||
Reference in New Issue
Block a user