delta/python-packages/sqlalchemy.git/lib/sqlalchemy/event/registry.py, branch workflow_test_foo github.com: zzzeek/sqlalchemy.git happy new year 2020-01-01T17:09:47+00:00 Mike Bayer mike_mp@zzzcomputing.com 2020-01-01T17:09:47+00:00 5881fd274015af3de37f2ff0f91ff6a7c61c1540 Change-Id: I08440dc25e40ea1ccea1778f6ee9e28a00808235 
Change-Id: I08440dc25e40ea1ccea1778f6ee9e28a00808235
Add new "exec_once_unless_exception" system; apply to dialect.initialize 2019-08-18T14:41:52+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-08-16T22:07:06+00:00 2051fa2ce9e724e6e77e19067d27d2660e7cd74a Fixed an issue whereby if the dialect "initialize" process which occurs on first connect would encounter an unexpected exception, the initialize process would fail to complete and then no longer attempt on subsequent connection attempts, leaving the dialect in an un-initialized, or partially initialized state, within the scope of parameters that need to be established based on inspection of a live connection. The "invoke once" logic in the event system has been reworked to accommodate for this occurrence using new, private API features that establish an "exec once" hook that will continue to allow the initializer to fire off on subsequent connections, until it completes without raising an exception. This does not impact the behavior of the existing ``once=True`` flag within the event system. Fixes: #4807 Change-Id: Iec32999b61b6af4b38b6719e0c2651454619078c 
Fixed an issue whereby if the dialect "initialize" process which occurs on
first connect would encounter an unexpected exception, the initialize
process would fail to complete and then no longer attempt on subsequent
connection attempts, leaving the dialect in an un-initialized, or partially
initialized state, within the scope of parameters that need to be
established based on inspection of a live connection.   The "invoke once"
logic in the event system has been reworked to accommodate for this
occurrence using new, private API features that establish an "exec once"
hook that will continue to allow the initializer to fire off on subsequent
connections, until it completes without raising an exception. This does not
impact the behavior of the existing ``once=True`` flag within the event
system.

Fixes: #4807
Change-Id: Iec32999b61b6af4b38b6719e0c2651454619078c
Add deprecation warnings to all deprecated APIs 2019-01-23T23:10:06+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-12-21T03:05:36+00:00 4c2c2c40fde17c85013e00a6f3303a99e2b32c12 A large change throughout the library has ensured that all objects, parameters, and behaviors which have been noted as deprecated or legacy now emit ``DeprecationWarning`` warnings when invoked. As the Python 3 interpreter now defaults to displaying deprecation warnings, as well as that modern test suites based on tools like tox and pytest tend to display deprecation warnings, this change should make it easier to note what API features are obsolete. See the notes added to the changelog and migration notes for further details. Fixes: #4393 Change-Id: If0ea11a1fc24f9a8029352eeadfc49a7a54c0a1b 
A large change throughout the library has ensured that all objects, parameters,
and behaviors which have been noted as deprecated or legacy now emit
``DeprecationWarning`` warnings when invoked.   As the Python 3 interpreter now
defaults to displaying deprecation warnings, as well as that modern test suites
based on tools like tox and pytest tend to display deprecation warnings,
this change should make it easier to note what API features are obsolete.

See the notes added to the changelog and migration notes for further
details.

Fixes: #4393
Change-Id: If0ea11a1fc24f9a8029352eeadfc49a7a54c0a1b
happy new year 2019-01-11T15:06:10+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-11T15:06:10+00:00 6f270fb0e344016ce526e0a1ecb3e3de9ffd1e3b Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911 
Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911
Post black reformatting 2019-01-06T23:23:11+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:19:47+00:00 1e278de4cc9a4181e0747640a960e80efcea1ca9 Applied on top of a pure run of black -l 79 in I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9, this set of changes resolves all remaining flake8 conditions for those codes we have enabled in setup.cfg. Included are resolutions for all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe 
Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe
Run black -l 79 against all source files 2019-01-06T17:34:50+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:14:26+00:00 1e1a38e7801f410f244e4bbb44ec795ae152e04e This is a straight reformat run using black as is, with no edits applied at all. The black run will format code consistently, however in some cases that are prevalent in SQLAlchemy code it produces too-long lines. The too-long lines will be resolved in the following commit that will resolve all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9 
This is a straight reformat run using black as is, with no edits
applied at all.

The black run will format code consistently, however in
some cases that are prevalent in SQLAlchemy code it produces
too-long lines.   The too-long lines will be resolved in the
following commit that will resolve all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9
Add before_mapper_configured event 2018-12-11T03:31:21+00:00 Chris Wilson chris+github@qwirx.com 2018-12-10T21:37:51+00:00 65ea042302693492cbaee96dfed5e9337e0d96a4 This event is intended to allow a specific mapper to be skipped during the configure step, by returning a value of `.orm.interfaces.EXT_SKIP` which means the mapper will be skipped within this configure run. The "new mappers" flag will remain set in this case and the configure operation will occur again. This event, and its return value, make it possible to query one base while a different one still needs configuration, which cannot be completed at this time. Fixes: #4397 Change-Id: I122e556f6a4ff842ad15315dcf39e19bb7f9a744 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4403 
This event is intended to allow a specific mapper to be skipped during the
configure step, by returning a value of `.orm.interfaces.EXT_SKIP` which means
the mapper will be skipped within this configure run. The "new mappers" flag
will remain set in this case and the configure operation will occur again.

This event, and its return value, make it possible to query one base while a
different one still needs configuration, which cannot be completed at this
time.

Fixes: #4397

Change-Id: I122e556f6a4ff842ad15315dcf39e19bb7f9a744
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4403
happy new year 2018-01-12T19:23:53+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-01-12T19:23:53+00:00 699272e4dcb9aa71ebbc0d9487fb6de82d3abc2b Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f 
Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f
update for 2017 copyright 2017-01-04T17:39:24+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-01-04T17:39:24+00:00 64e72b58fd74db0c5c87407c824d08ad699e5e8e Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de 
Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de
- happy new year 2016-01-29T16:20:22+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-01-29T16:20:22+00:00 859379e2fcc4506d036700ba1eca4c0ae526a8ee