Chuck Cadman

@mroeschke, I found another bug in addition to the one I intend to resolve with #49967. The second bug is with `pandas.io.sql.execute`. If the caller passes a query that returns...

Another potential solution to the `pandas.io.sql.execute` bug is to use `freeze` to fetch all the results before cleaning up. This is inefficient, and I will update the usage docs to...

Status update: I think this is ready, but it has two PRs in front of it (#50177 and #49967) and I'm still not getting the CI checks to all pass.

There is one failing test unrelated to the changes I am making. I welcome any suggestions: ``` pandas/tests/io/parser/common/test_file_buffer_url.py::test_file_descriptor_leak[c_high] - AssertionError: ([], [pconn(fd=17, family=, type=, laddr=addr(ip='10.1.0.145', port=36288), raddr=addr(ip='140.82.112.4', port=443), status='ESTABLISHED')]) ```

@phofl , the first commit is split off in a separate PR: #49967 . I could make a new PR for the second commit, as it is a separate item:...

I had turned off SQLALCHEMY_WARN_20. I will turn it back on and debug these warnings.

@phofl , the tests are now passing with SQLALCHEMY_WARN_20 set to 1. They also pass under sqlalchemy version 2.0.0rc1.

@moritzmeister , I was hoping it could be included in pandas 1.5.3, but the decision was not to include it: https://github.com/pandas-dev/pandas/issues/49857#issuecomment-1374889050 . For your issue, I am surrounding the query...

In the `if TYPE_CHECKING` block, the `myfunc` property is set to `None`, which is not callable. So the underlying issue is that pylint is using the `if TYPE_CHECKING` block to...

Yes, `DeprecationWarning` is ignored by python's default warning filter, so I used the `-Walways` to make it print out. I first noticed the warnings in `pytest` logs for some code...