-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEPR: revert enforcing the deprecation of exposing blocks in core.internals and deprecate with FutureWarning #58715
Conversation
…nWarning with FutureWarning
I reverted the removal of @jorisvandenbossche could you please take a look at my changes? Is that what you meant in your comment in #58467? |
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
Looks like this PR is fairly stale so closing to clear the queue, but happy to reopen at a later time |
…osing-blocks-core-internals-replace-DeprecationWarning-FutureWarning
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
…osing-blocks-core-internals-replace-DeprecationWarning-FutureWarning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the slow follow-up, but thanks for the PR @natmokval!
(accidentally added this to the 2.3 milestone instead of 3.0, this change of course does not need to be backported because the related change is only on main) |
…ernals and deprecate with FutureWarning (pandas-dev#58715)
xref #58467