hatch env creation currently broken (placeholder issue)

[kratsg]

Please see pypa/virtualenv#2735 for the upstream problem. However, a lot of people using hatch will see this crash at the hatch level and it's not very obvious.

I'm not sure how to restrict hatch to use a specific version of filelock when it creates environments.

[EarningsCall]

Please see pypa/virtualenv#2735 for the upstream problem. However, a lot of people using hatch will see this crash at the hatch level and it's not very obvious.

I'm not sure how to restrict hatch to use a specific version of filelock when it creates environments.

In your setup scripts, you can just do this for now (until they fix the issue)

pip install --upgrade hatch filelock==3.14.0

[kratsg]

I'm not sure this works for me, as hatch is pulling in filelock when it builds an environment. I can try quickly to see. From gitlab CI, this is what i have

$ python -m pip freeze --local
argcomplete==3.3.0
click==8.1.7
packaging==24.0
pipx==1.6.0
platformdirs==4.2.2
userpath==1.9.2
$ pipx run hatch run build-check
creating virtual environment...
creating shared libraries...
upgrading shared libraries...
installing hatch...
Creating environment: default
Installing project in development mode
Checking dependencies
Syncing dependencies
cmd [1] | python -m build
...

so I don't have filelock by default in the original environment that pipx is using. In this case, I will need to likely to

pipx inject --force hatch filelock==3.14.0

so I will try that!

EDIT: filelock 3.15.0 got yanked: https://pypi.org/project/filelock/3.15.0/ .

[ofek]

Thank you! Closing as the release got yanked.