Skip to content
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

bpo-45132 Remove deprecated __getitem__ methods #28225

Merged
merged 4 commits into from Sep 8, 2021

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Sep 7, 2021

Remove deprecated __getitem__ methods of xml.dom.pulldom.DOMEventStream, wsgiref.util.FileWrapper and fileinput.FileInput, deprecated since Python 3.9.

https://bugs.python.org/issue45132

Remove deprecated __getitem__ methods of xml.dom.pulldom.DOMEventStream,
wsgiref.util.FileWrapper and fileinput.FileInput, deprecated since Python 3.9.
Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

LGTM, but I have some documentation nitpicks.

Doc/library/fileinput.rst Outdated Show resolved Hide resolved
Doc/library/fileinput.rst Outdated Show resolved Hide resolved
Doc/library/wsgiref.rst Outdated Show resolved Hide resolved
Doc/library/wsgiref.rst Outdated Show resolved Hide resolved
Doc/library/wsgiref.rst Outdated Show resolved Hide resolved
Doc/library/xml.dom.pulldom.rst Outdated Show resolved Hide resolved
hugovk and others added 2 commits Sep 8, 2021
`deprecated-removed` is only used for future planned removing. After removing it is just `versionchanged`.

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Insert "In addition it is :term:`iterable` and has a ..."

deprecated-removed is only used for future planned removing.
After removing it is just versionchanged.
@hugovk
Copy link
Member Author

@hugovk hugovk commented Sep 8, 2021

@serhiy-storchaka Thanks for the review, updated! Let me know if I should squash the commits or anything like that.

Thanks also for the guidance about deprecated-removed / versionchanged. I'd checked deprecated-removed in the devguide but it didn't say it's only for pre-removal; I'll make a PR to update the devguide.

https://devguide.python.org/documenting/?highlight=deprecated-removed#paragraph-level-markup

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

After removing deprecated features we remove deprecated directives.

@hugovk
Copy link
Member Author

@hugovk hugovk commented Sep 8, 2021

After removing deprecated features we remove deprecated directives.

Ah right, so should I do this too?

-   .. deprecated:: 3.8
+   .. versionchanged:: 3.8
      Support for :meth:`__getitem__` method is deprecated.

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Sep 8, 2021

Replace deprecated with versionchanged, is deprecated with has been removed (or something like), and move the directive down if necessary. Since you already added versionchanged directives, just remove corresponding deprecated directives. They are not of interest to users of future Python versions.

Doc/library/fileinput.rst Outdated Show resolved Hide resolved
Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

LGTM

@serhiy-storchaka serhiy-storchaka merged commit d003a5b into python:main Sep 8, 2021
12 checks passed
@hugovk hugovk deleted the rm-deprecated-__getitem__ branch Sep 8, 2021
@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Sep 8, 2021

After reading the devguide I am no longer sure about deprecated-removed. Maybe I always used it incorrectly. Or its semantic was changed with time. It needs additional discussion.

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Sep 8, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants