Skip to content

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

Merged
ksunden merged 1 commit into
matplotlib:mainfrom
QuLogic:no-in-removal
Sep 25, 2024
Merged

ksunden merged 1 commit into
matplotlib:mainfrom
QuLogic:no-in-removal

Conversation

@QuLogic

@QuLogic QuLogic commented Sep 25, 2024 •

Copy link
Copy Markdown
Member

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
@QuLogic
QuLogic deleted the no-in-removal branch September 25, 2024 21:12
kc9323 pushed a commit to kc9323/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