pythonpython-attrs/cattrs #275Not a task: already works

Should cattrs keep the Python version uncapped?

envgap__python-attrs__cattrs-275

Original GitHub issue ↗Dated source checkout ↗Opened 2022-06-17

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: a10ad1c638dd16308c9aa73c649fa92282503c00
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

python-attrs/cattrs #275 · read the original issue

* 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?

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]