Skip to content

Dependencies are rather strict, leading to conflicts #449

@maresb

Description

@maresb

The requirement packaging>=21.3 makes Hatch impossible to install it alongside Poetry 1.1. (Here the blame is definitely not entirely on Hatch!)

Also, click>=8.0.3 is less than a year old, and occasionally some package may pin click <8.

Since Hatch is a build tool which may be used in large environments alongside older dependencies, it would in general be nice if its dependencies were left a bit looser, perhaps vendoring newly introduced functionality. Or does Hatch make essential use of these new versions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions