'hatch env hash'?

[kpfleming]

I'd like to be able to use something like hatch dep hash, but for specific environments (either one, or a list of them) instead of all environments.

In addition, I'd like it to include all environment options which affect how Hatch would populate the environment (e.g. skip-install). Essentially, I want to be able to know whether Hatch would make any changes to an existing environment based only the configuration, not package indexes or other external factors.

Would this be practical to implement?

My goal is to improve my 'build images in advance' workflow, which pre-creates a number of the environments defined in pyproject.toml. When I make changes to that file, I have to rebuild the image, even though most of the content in there does not affect the image content; if I could learn from Hatch itself a 'hash' of the configuration and dependencies for each environment, I could compare that to the hash when the image was last built and avoid rebuilding if the hash has not changed.

[ofek]

Yeah I would be fine with that, sounds like a good idea

[kpfleming]

Thanks. I'll have to put this on my 'research' list for next month, the list is already quite long :-)