Dependencies are rather strict, leading to conflicts

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

[ofek]

• click 8.0.1 is required for windows_expand_args=False
• packaging I plan to upgrade when the next release happens for decreased import time of Hatch and the extras change Hatchling will benefit from https://packaging.pypa.io/en/latest/changelog.html

[ofek]

decreased import time

$ python -m timeit -n 1 -r 1 "import packaging.requirements"
1 loop, best of 1: 41 msec per loop
$ python -m pip install -qqq git+https://github.com/pypa/packaging
$ python -m timeit -n 1 -r 1 "import packaging.requirements"
1 loop, best of 1: 26.4 msec per loop

[maresb]

Hmm, if you're eager to always pin Hatch dependencies to recent versions and not support compatibility hacks, then perhaps it'd be helpful to more prominently recommend installing Hatch via pipx?

[ofek]

eager to always pin Hatch dependencies to recent versions

Not really, more so eager to enforce fixes or features that directly affect Hatch. I don't set minimum versions arbitrarily 😉