Skip to content

Do we need a "low" or "stable" set of dependencies? #192

@rsyring

Description

@rsyring

We had a stable set of dependencies that was used in the tests.

I removed them when modernizing b/c it seems somewhat of a legacy construct. I believe I used to do that in case something broke in the future I'd know what the last set of deps that passed was. However, with CI, we can just go back to the logs and see what set of deps passed last.

We could do a minimum version tests, which is what Pallets projects do. Example:

https://github.com/pallets/flask/blob/85c5d93cbd049c4bd0679c36fd1ddcae8c37b642/pyproject.toml#L195

I'm inclined to not put the stable tests back and not run "low" tests unless we run into a situation where it helps to have them. If that situation hasn't shown up in the next year or so, we can close this issue.

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