`utcnow` deprecation note is misleading

Documentation

Currently, the deprecation notice for datetime.utcnow() reads:

Deprecated since version 3.12: Use datetime.now() with UTC instead.

Unfortunately, applying this suggestion verbatim can easily break user code – especially when applying it to libraries. (See for example https://foss.heptapod.net/openpyxl/openpyxl/-/issues/2051). These datetime-related TypeErrors are easy to introduce, and fairly hard to fix. I suggest to amend the deprecation notice:

Deprecated since version 3.12: Use datetime.now(UTC) instead. Please note that this will return an aware datetime object. If you need to remain compatible, use datetime.now(UTC).replace(tzinfo=None).

Maybe someone can come up with a better wording.

Linked PRs

• gh-118571

リンク先の datetime ページにある datetime.datetime.utcnow() のドキュメントを確認し、提案された文言を PR gh-118571 と比較します。deprecation note が datetime.now(UTC) は aware datetime を返すことを明確に警告し、互換性のための replace(tzinfo=None) オプションを記載するか、合意されたよりよい文言を採用すれば完了です。