Skip to content

clarify distinction between datetime module and class in deprecation messages (again) #109080

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

Conversation

neutrinoceros
Copy link
Contributor

follow up to #108073, in response to @ellert's comment #108073 (comment)

I think this time we have all of them.

@ellert
Copy link

ellert commented Sep 7, 2023

I think this time we have all of them.

Line 1816....

@neutrinoceros neutrinoceros force-pushed the consistent_datetime_depr_warnings branch from 59c4eb0 to 6f22f49 Compare September 7, 2023 13:35
@neutrinoceros
Copy link
Contributor Author

fixed, but next time please consider asking nicely.

@neutrinoceros
Copy link
Contributor Author

ping @Yhg1s for merge ?

@neutrinoceros
Copy link
Contributor Author

I think I saw a thread on https://discuss.python.org/ at some point, discussing whether warning messages should be exactly preserved in between patch releases, however I wasn't able to find it back. Surely it would clarify if this PR is even wanted.
I'm still going to rebase it to resolve a small merge conflict while I'm in there, but please just close this if it's not acceptable by current policies.

@neutrinoceros
Copy link
Contributor Author

Oh actually it's not just any conflict: my PR is completely superseded by #114761, so no reason to keep it around !

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.

4 participants