Skip to content

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Sep 8, 2025

@sethmlarson
Copy link
Contributor

Reviewed the SBOM changes.


.. Add deprecations above alphabetically, not here at the end.
.. include:: ../deprecations/pending-removal-in-3.16.rst

.. include:: ../deprecations/pending-removal-in-3.17.rst
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this will show the same list twice in this page?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that's how we're already doing it for other ones (I'm not sure if we should, but that's another discussion).

Copy link
Member

@merwok merwok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for this!

Copy link
Member

@vsajip vsajip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with the logging-related changes, thank you.

if name == "__version__":
from warnings import _deprecated

_deprecated("__version__", remove=(3, 17))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PEP 387 says:

It is preferred, though, to wait 5 years before removal (e.g., warn starting in Python 3.10, removal in 3.15; this happens to coincide with the current lifetime of a minor release of Python).

Suggested change
_deprecated("__version__", remove=(3, 17))
_deprecated("__version__", remove=(3, 20))

Or is there a reason to rush this?

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.

5 participants