Skip to content

Stop hardcoding exact versions in pyproject.toml #4694

Description

@C0rn3j

pip check fails on my system because the project currently hardcodes dependencies to specific versions:

$ pip check
archinstall 4.4 has requirement cryptography==48.0.1, but you have cryptography 49.0.0.
archinstall 4.4 has requirement markdown-it-py==4.0.0, but you have markdown-it-py 4.2.0.
archinstall 4.4 has requirement textual==8.2.7, but you have textual 8.2.8.

The deps should all iirc be >= , to allow that version as a minimum one and any version coming after it.
Or stop defining a version altogether.

If you wish to provide a set of deps that the project is guaranteed to work with, use pylock.toml (or uv's own lockfile system) - https://packaging.python.org/en/latest/specifications/pylock-toml/#pylock-toml-spec

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