delta/python-packages/sqlalchemy.git/lib/sqlalchemy/pool/dbapi_proxy.py, branch rel_1_4 github.com: zzzeek/sqlalchemy.git happy new year 2023 2023-01-03T17:50:29+00:00 Mike Bayer mike_mp@zzzcomputing.com 2023-01-03T17:50:29+00:00 4f5970525403c98d46ed1a60f7816bc413a8c523 Change-Id: I14db8e9c69a832b0f5dae8036db3c0a70bb49edd 
Change-Id: I14db8e9c69a832b0f5dae8036db3c0a70bb49edd
happy new year 2022 2022-01-06T20:59:47+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-01-06T20:59:47+00:00 2f370229d63665ffae72a9f8a37800b4d70cf6a1 Change-Id: Ic38dbc640aa0fe8a784a5b5e57c45a41eb0ea01b 
Change-Id: Ic38dbc640aa0fe8a784a5b5e57c45a41eb0ea01b
Replace all http:// links to https:// 2021-07-04T18:54:33+00:00 Federico Caselli cfederico87@gmail.com 2021-07-04T17:29:19+00:00 fb81f9c8d914f9911925dd3f4e77d7fc374b267c Also replace http://pypi.python.org/pypi with https://pypi.org/project Change-Id: I84b5005c39969a82140706472989f2a30b0c7685 
Also replace http://pypi.python.org/pypi with https://pypi.org/project

Change-Id: I84b5005c39969a82140706472989f2a30b0c7685
happy new year 2021-01-04T14:47:43+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-01-04T14:47:43+00:00 640cd8a70f8a664b7834c5f74ec322fdea644043 Change-Id: Ic5bb19ca8be3cb47c95a0d3315d84cb484bac47c 
Change-Id: Ic5bb19ca8be3cb47c95a0d3315d84cb484bac47c
Merge "Use context managers for threading.Lock()" 2020-01-03T21:49:49+00:00 mike bayer mike_mp@zzzcomputing.com 2020-01-03T21:49:49+00:00 c0352b03e840ddf68116182b22c5fd4eac2059cf 






Use context managers for threading.Lock()
2020-01-03T18:09:46+00:00

Heckad
heckad@yandex.ru

2020-01-01T19:47:01+00:00

a076b1f30406cbb59a55e2c01ddd17a84636778e

(zzzeek:) For some reason I thought that threading.Lock() still did
not support context managers, at least in Python 2, however this
does not seem to be the case.

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Closes: #5069
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5069
Pull-request-sha: efeac06dda5afdbe33abcf9b27c8b5b5725c8444

Change-Id: Ic64fcd99cd587bc70b4ecc5b45d8205b5c76eff2





(zzzeek:) For some reason I thought that threading.Lock() still did
not support context managers, at least in Python 2, however this
does not seem to be the case.

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Closes: #5069
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5069
Pull-request-sha: efeac06dda5afdbe33abcf9b27c8b5b5725c8444

Change-Id: Ic64fcd99cd587bc70b4ecc5b45d8205b5c76eff2







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 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