Skip to content

Should cattrs keep the Python version uncapped? #275

@madig

Description

@madig
  • cattrs version: 22.1.0 and main
  • Python version: 3.8.x
  • Operating System: Windows 10 x64

Description

I recently read https://iscinumpy.dev/post/bound-version-constraints/ and wanted to follow the advice to keep the Python version uncapped. I prompty stumbled over the problem described in https://iscinumpy.dev/post/bound-version-constraints/#pinning-the-python-version-is-special because cattrs does python = "^3.7" instead of python = ">=3.7". I wonder if it should declare the latter?

Metadata

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