Skip to content

Fix the use of versionadded and versionchanged directives #115664

Closed
@serhiy-storchaka

Description

@serhiy-storchaka

While reviewing the PR for #115652 I noticed other errors in multiprocessing.rst: incorrect order of versionchanged directives, using versionadded instead of versionchanged, misusing the term "argument" instead of "parameter". Then I tried to search similar errors in other files, and found tens possible candidates. So I opened an issue to fix all these errors.

versionadded indicates when the entity (module, class, function, method, attribute, etc) was added. It should be aligned with the description of the entity.

versionchanged indicates when the behavior of the entity was changed, including adding or removal of parameters or support of protocols. When a new parameter is added to the function or when the class starts supporting the context manager protocol, versionchanged should be used. If a new attribute or method was added, but they do not have their own entry, versionchanged can be used, applied to the parent class.

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.11only security fixes3.12only security fixes3.13bugs and security fixesdocsDocumentation in the Doc dir

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions