Ofek Lev
Ofek Lev
Yes please
My instinct is to close this because it's up to the user whether or not they require such features and therefore may not be compliant with the spec i.e. users...
Okay, how does this sound: when Hatch introduces workspaces (which would be what users actually want) then I will change the functionality in Hatchling to be such that an option...
Actually wait, that is the current behavior because Hatchling will by default error for direct references such as local paths. So back to the beginning I suppose all I can...
I don't know how to make the situation better than a doubly opt-in option. I could of course remove the feature but then there are users that require it.
Does it work if you do `hatch new project .`?
I'm totally open to someone adding a `-f`/`--force` flag!
Hatchling supports multiple [modes](https://hatch.pypa.io/1.13/config/build/#dev-mode) for development installations. The [mechanism](https://editables.readthedocs.io/en/latest/usage.html#adding-a-directory-as-package-content) I think you're referencing is not currently supported after taking a quick look at the [logic](https://github.com/pypa/hatch/blob/hatchling-v1.27.0/backend/src/hatchling/builders/wheel.py#L541-L546). PRs always welcome! I haven't...
https://github.com/pypa/hatch/pull/1576
Hey there! I would recommend creating a third-party build hook: https://hatch.pypa.io/latest/plugins/build-hook/reference/