How to use python version in lock filename?

[ketozhang]

Looking at hatch context variables documented in https://hatch.pypa.io/latest/config/environment/overview/ I can't seem to find a way to also write out the python version for the lock file.

[oprypin]

I think the only way to get the Python version is through the matrix.

Example how to get it into the env name -> into the lock filename:

[tool.hatch.envs.exampleenv]
type = "pip-compile"
[[tool.hatch.envs.exampleenv.matrix]]
python = ["3.11"]

I was also writing this example:

[tool.hatch.envs.exampleenv]
type = "pip-compile"
lock-filename = "requirements/requirements-{env_name}.{matrix:examplevarname}.txt"
[[tool.hatch.envs.exampleenv.matrix]]
examplevarname = ["3.11"]

but actually the latter part is redundant, the version is part of the env anyway and then it's part of the filename twice

[ketozhang]

What if I don't set matrixes version?

[oprypin]

Then I think you can't get it as part of the file name, you only get it as text inside the lock file. What's your use case?

[juftin]

This repo uses a python matrix:

hatch-pip-compile/pyproject.toml

Lines 117 to 118 in f7d9dad

	[[tool.hatch.envs.matrix.matrix]]
	python = ["3.8", "3.9", "3.10", "3.11", "3.12"]

The resulting locks are automatically created with py3.x as part of their filename: i.e. requirements-matrix.py3.12.txt

---

Unless you're leveraging matrices there's not currently a way (apart from harcoding in your lock-filename variable) to get the Python version into the lockfile name as {python_version} isn't currently part of the context variables available.

---

Could you tell me a bit more about your use case? Are you looking to have multiple lockfiles per environment for non-matrix environments?

[ketozhang]

Thinking about my use case a bit more, I should be using matrices if I want multiple python-version lockfiles.

If you're curious my use case was:

I'm using this for test environments for developing a private package that I have full control over. I have no use for matrices because I own all applications that uses private package therefore I only need to support a single Python version. However as new Python version comes out, I do increment the package's requires-python and the application server's Python. With this I want to keep a historical version of lock files.

I am convinced I should just use 1 lock file and I can always use git history to go back to a previous version.

Thanks you two!