Skip to content

pan out deprecations and plan for backward compat breaks #3737

@RonnyPfannschmidt

Description

@RonnyPfannschmidt

i noticed that our list of removed in pytest 4.0 deprecation's gets painstakingly long
i believe its time to set up a Removed in 5.0 warning and make some choices that we can go along with in a few months of time and do the actual removal

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: backward compatibilitymight present some backward compatibility issues which should be carefully noted in the changelogtype: feature-branchnew feature or API change, should be merged into features branch

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions