After a version bump, how can I get the new version inside a virtual env?

[brutus]

When I work on a project with hatch and increase it's version number, Python code seems to never pick up this change until the environment is removed/purged. I used the default with the dev-mode = true first, but changing dev-mode = false seems to not change this.

Is this expected or am I missing something?

Here's a minimal Example:

I created a new project…

% hatch new foobar
foobar
├── src
│ └── foobar
│ ├── __about__.py
│ └── __init__.py
├── tests
│ └── __init__.py
├── LICENSE.txt
├── README.md
└── pyproject.toml

But changed the generate pyproject.toml to use a static version:

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "foobar"
description = ''
readme = "README.md"
requires-python = ">=3.7"
license = "MIT"
dependencies = []
version = "1.6.1"

# …

Checking the version once is fine:

% hatch run python -c 'import importlib.metadata; print(importlib.metadata.version("foobar"))'
1.6.1

But after incrementing my version (manually in pyproject.toml), I still get
the same results.

If I ask hatch directly about it, it's recent though:

% hatch version
1.6.2

Maybe, when I set it:

% hatch version 1.6.3
Cannot set version when it is statically defined by the `project.version` field

BTW: is this expected behavior?

When I use a dynamic version instead, getting and setting it with hatch went fine alright, but I still only ever get the first version from importlib.….

Running hatch env prune after setting a version seems to work tough.

[ofek]

This is a Python issue rather than specific to Hatch, package metadata is not dynamic but is saved at the time of installation