Skip to content

Consider requires_python with patch release #7

Open
@thatch

Description

If a constraint looks like full_python_version >= "3.5.2" and the requires_python on the target release is >=3.5.3, should it be included? I think most projects would specify a patch version because an earlier patch release was too broken to use, but they tend to fall out of use very quickly. Are there other uses?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions