Jarek Potiuk

> Instead, what do you think about adding a context manager on the metadata class for temporarily setting a property which could be used here? https://github.com/pypa/hatch/blob/hatchling-v1.24.2/backend/src/hatchling/builders/plugin/interface.py#L89-L90 Yes. it will remove...

Smth like that ?

Or did you think to bubble it up to BuilderInterface ?

Hmm. A bit of a problem there is that we do not necessarily have to run `build` method. What I **really** am after is to be able to get the...

I can't remember the full execution path - but every time ` self.builder.metadata.core` in BuilderConfig is accessed, the "update_metadata" hook is called (way before `for loop§ is entered.

Some more details @ofek - Even if `build()` method is called on `BuildInterface` - what happens here, that "metadata_hook" is called during `validate_fields` - so way before we enter the...

I have [experimented](https://github.com/potiuk/hatch/commit/c02df17da7d0305d0b92c0fdd17dd3d4c8135346) a bit more with different approach: where `update_metadata` hook would be called several times - potentially - when version is retrieved during `validate_fields()` at the beginning of...

> Okay I thought about this and have a really good idea! I think this build indicator should be an environment variable that the caller sets. This would mean the...

Yep. Understood :)

Sure: imagine we have `logging` package with several modules: * airflow.shared.logging/main.py * airflow.shared.logging/communicate.py And main.py does "from airflow.shared.logging.communicate import something" And imagine we want to install two distributions: * airflow-core...