Skip to content
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: do not try to predict removal dates in deprecation warnings by default #4252

Merged

Conversation

neutrinoceros
Copy link
Member

PR Summary

A hard-learned lesson from yt 4.1 was that making promises about when deprecated features would be removed can sometimes come back at us and make releases much more difficult to polish.
In most recent feature releases (4.0, 4.1, and soon 4.2), we made some eager cuts through stuff that was deprecated in the previous 7 or so years, but long term it's probably better to just not try to anticipate too accurately when deprecated code is actually going to be removed, and we can probably just live with it as long as it doesn't impede further developments.

@neutrinoceros neutrinoceros added deprecation deprecate features or remove deprecated ones enhancement Making something better labels Dec 17, 2022
@neutrinoceros neutrinoceros added this to the 4.2.0 milestone Dec 17, 2022
@neutrinoceros neutrinoceros marked this pull request as ready for review December 17, 2022 17:21
@neutrinoceros neutrinoceros force-pushed the no_predictions_in_depr_messages branch from c00a823 to 8c2ee96 Compare December 18, 2022 11:07
@neutrinoceros neutrinoceros merged commit 2770642 into yt-project:main Dec 22, 2022
@neutrinoceros neutrinoceros deleted the no_predictions_in_depr_messages branch December 22, 2022 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecation deprecate features or remove deprecated ones enhancement Making something better
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants