Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Remove 'in' from removal substitution for deprecation messages #28880

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

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Sep 25, 2024

PR summary

Ever since #27702, the removal will always be a version, and not "two minor/meso releases later". The implicit "to" tends to get messed up by people writing custom message arguments, and since there's no reason to add the "to" into removal instead of in the message any more, move it to the message.

Also, fix the autogenerated message to follow what the docstring says (Falsy removal leaves out the removal date.)

PR checklist

Ever since matplotlib#27702, the removal will always be a version, and not "two
minor/meso releases later". This tends to get messed up by people writing
custom `message` arguments, and since there's no reason to add the "to"
there instead of in the message any more, move it to the message.

Also, fix the autogenerated message to follow what the docstring says
(Falsy `removal` leaves out the removal date.)
@ksunden ksunden added this to the v3.10.0 milestone Sep 25, 2024
@ksunden ksunden merged commit e43e0bd into matplotlib:main Sep 25, 2024
44 of 46 checks passed
@QuLogic QuLogic deleted the no-in-removal branch September 25, 2024 21:12
kyracho pushed a commit to kyracho/matplotlib that referenced this pull request Oct 10, 2024
…otlib#28880)

Ever since matplotlib#27702, the removal will always be a version, and not "two
minor/meso releases later". This tends to get messed up by people writing
custom `message` arguments, and since there's no reason to add the "to"
there instead of in the message any more, move it to the message.

Also, fix the autogenerated message to follow what the docstring says
(Falsy `removal` leaves out the removal date.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants