DEPR: ADD FutureWarning for pandas.io.execute #50676
Conversation
…/github.com/luke396/pandas into add-FutureWarning-for-pandas.io.sql.execute
|
@phofl, sorry again, we can start over here! I'm not sure if it's appropriate and polite for me to start a new PR directly, if not, please let me know directly |
phofl
changed the title
|
It's fine :) Thanks for continuing, looks good generally, we are holding off on merging deprecations, so will merge when we are ready with our old deprecations |
|
I apologize if my change has caused the check failure below again. Could you kindly inform me if it is related, and guide me on how to resolve it? If my change is not related, there is no need to respond. I greatly appreciate your help with this matter. |
phofl
added
IO SQL
|
thx @luke396 failures were unrelated |
I've noticed that you all are working hard to fix the CI issues. Keep up the good work! 😄 |
| @@ -556,9 +556,10 @@ Other API changes | |||
| Deprecations | |||
| ~~~~~~~~~~~~ | |||
| - Deprecated argument ``infer_datetime_format`` in :func:`to_datetime` and :func:`read_csv`, as a strict version of it is now the default (:issue:`48621`) | |||
| - Deprecated :func:`pandas.io.sql.execute`(:issue:`50185`) | |||
There was a problem hiding this comment.
I think may need a space to render properly?
reopen for DEPR: Add FutureWarning for pandas.io.sql.execute Pull Request #50638
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.