delta/python-packages/sqlalchemy.git/lib/sqlalchemy/ext/declarative, branch flake8_12

- flake8 for lib passes

2019-01-05T22:00:18+00:00

Change-Id: I0d7f5105f838a0275f3c240441bdcdc9ae7444d0

flake8 refactor - ext

2019-01-05T21:38:21+00:00

A full rewrite of all imports and pep8 formatting using zimports, black,
commits are broken into sections.

Directories included in this commit:

    lib/sqlalchemy/ext/

Change-Id: I3dd7aed3f42675e9ada64446ffd2758db7c3bc93
(cherry picked from commit 0716a292e03040ad4f96b890691b9e2c888ec11d)

- do a broken zimports run on lib

2019-01-05T17:24:39+00:00

step 1, straight black -l 79 run

2019-01-05T17:06:50+00:00

includes adjustment to setup.py to recognize __version__ correctly

"left" -> "accidentally placed at"

2018-12-02T23:59:45+00:00

since "left" is kind of ambiguous, use more explicit terminology
here.

Also update the test to use a positive assertion that the
warning is emitted; quote the attribute name.

Change-Id: Ic2284c200a26b32b2da063cfaf6d59547309d587
References: https://github.com/zzzeek/sqlalchemy/pull/488
(cherry picked from commit eacb31a89fe883edd0ada7f2724239c1f8c5b685)

Warn for lower-case column attribute on declarative

2018-11-26T06:12:59+00:00

A warning is emitted in the case that a :func:`.column` object is applied to
a declarative class, as it seems likely this intended to be a
:class:`.Column` object.

Fixes: #4374
Change-Id: I2e617ef65547162e3ba6587c168548ad0cf6203d
(cherry picked from commit 6ec40eca1a03a9156ee82f3ce75850778220b39e)

Move pk on single-inh subclass check below conflict resolution check

2018-10-30T17:31:53+00:00

The column conflict resolution technique discussed at
:ref:`declarative_column_conflicts` is now functional for a :class:`.Column`
that is also a primary key column.  Previously, a check for primary key
columns declared on a single-inheritance subclass would occur before the
column copy were allowed to pass.

Fixes: #4352
Change-Id: Id4c025da53c28e58db6b549fe398f25f8a90d355
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/483
(cherry picked from commit 3ed79a5c18c14d842280805d1dae8a9c99ec8f18)

Check more specifically for hybrid attr and not mapped property

2018-10-20T16:15:34+00:00

Fixed regression caused by :ticket:`4326` in version 1.2.12 where using
:class:`.declared_attr` with a mixin in conjunction with
:func:`.orm.synonym` would fail to map the synonym properly to an inherited
subclass.

Fixes: #4350
Change-Id: Ib2a9b6a125a2ac7c7ff80201746b7f10e5596226
(cherry picked from commit 9335c24d6c98033f4aa1ceafd23a70b88c8ae811)

Unwrap Proxy objects when scanning declared_attr

2018-08-23T16:47:24+00:00

Fixed bug where the declarative scan for attributes would receive the
expression proxy delivered by a hybrid attribute at the class level, and
not the hybrid attribute itself, when receiving the descriptor via the
``@declared_attr`` callable on a subclass of an already-mapped class. This
would lead to an attribute that did not report itself as a hybrid when
viewed within :attr:`.Mapper.all_orm_descriptors`.

Fixes: #4326
Change-Id: I582d03f05c3768b3344f93e3791240e9e69b9d1e
(cherry picked from commit 626356842d77d4ec6427b3bfc04bdff93d24d246)

Accommodate for classically mapped base classes in declarative

2018-08-17T17:42:02+00:00

Fixed issue in previously untested use case, allowing a declarative mapped
class to inherit from a classically-mapped class outside of the declarative
base, including that it accommodates for unmapped intermediate classes. An
unmapped intermediate class may specify ``__abstract__``, which is now
interpreted correctly, or the intermediate class can remain unmarked, and
the classically mapped base class will be detected within the hierarchy
regardless. In order to anticipate existing scenarios which may be mixing
in classical mappings into existing declarative hierarchies, an error is
now raised if multiple mapped bases are detected for a given class.

Fixes: #4321
Change-Id: I8604ecfd170d2589d9d1b1c87ba303762071fc30
(cherry picked from commit 4c931b2ec7e0f09ac8c3ebe28c794f5858d54efb)