pypa
Does metadata get synced on every `hatch run`?
Some people like to have their in-dev package version to accurately reflect the number of commits made since the last version tag. They usually rely on crutches like calculating the conventional __version__ variable at runtime.
Since #1017, you no longer update the environment dependencies if the specs didn’t change, but are you updating package metadata?
If not, maybe there’s a way to do that fast enough that it can be done on every hatch run so people who care about it being up-to-date have a better alternative than relying on __version__.
Even before then project metadata was never updated, only dependencies. I suppose I could add an option to environments where running would first do pip install --no-deps -e .
I think a better solution would be an option within Hatchling where editable installations had dynamic metadata. This has been requested before as a broadly desired feature even outside of Hatch but I haven't thought of how to go about that yet. It would definitely be logic inside a .pth file though.
