delta/python-packages/sqlalchemy.git/test/engine/test_logging.py, branch flake8_12

zimports for all of test/

2019-01-05T17:13:02+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

Make all tests to be PEP8 compliant

2017-02-07T16:21:56+00:00

tested using pycodestyle version 2.2.0

Fixes: #3885
Change-Id: I5df43adc3aefe318f9eeab72a078247a548ec566
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/343

Support python3.6

2017-01-13T15:57:41+00:00

Corrects some warnings and adds tox config.  Adds DeprecationWarning
to the error category.   Large sweep for string literals w/ backslashes
as this is common in docstrings

Co-authored-by: Andrii Soldatenko
Fixes: #3886
Change-Id: Ia7c838dfbbe70b262622ed0803d581edc736e085
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/337

- handle parameter sets that aren't correctly formed, so that

2016-02-17T21:53:01+00:00

for example an exception object made within a test suite can
still repr (error seen in Keystone)

- do the trailing comma logic of tuple repr() exactly

2016-02-17T20:21:00+00:00

- All string formatting of bound parameter sets and result rows for

2016-02-17T18:31:29+00:00

logging, exception, and  ``repr()`` purposes now truncate very large
scalar values within each collection, including an
"N characters truncated"
notation, similar to how the display for large multiple-parameter sets
are themselves truncated.
fixes #2837

- Exception messages have been spiffed up a bit. The SQL statement

2014-10-17T23:37:45+00:00

and parameters are not displayed if None, reducing confusion for
error messages that weren't related to a statement.  The full
module and classname for the DBAPI-level exception is displayed,
making it clear that this is a wrapped DBAPI exception.  The
statement and parameters themselves are bounded within a bracketed
sections to better isolate them from the error message and from
each other.
fixes #3172

- Fixed bug in connection pool logging where the "connection checked out"

2014-08-20T16:01:20+00:00

debug logging message would not emit if the logging were set up using
``logging.setLevel()``, rather than using the ``echo_pool`` flag.
Tests to assert this logging have been added.  This is a
regression that was introduced in 0.9.0.
fixes #3168

- pep8 cleanup

2014-08-20T13:08:59+00:00