Henry Schreiner
Henry Schreiner
I believe we had this idea at the beginning, got stuck on if it should set _DIR or _ROOT, and then somehow didn't end up adding either... IIRC _ROOT is...
We've been supporting directly specifying the directory and not requiring an entry point function. It just needs to be a valid Python module, which is pretty much just a directory.
Ahh, but a module path could resolve to several physical paths. But I think we could just then pick the one with the config file in it?
> I think Henry was referring to the fact that with the `cmake.prefix` entrypoint projects just specify a module Yes, also `cmake.module`. These work by simply providing the module that...
If you wanted to point at `.../lib/...` vs. `.../lib64/...`, it would quite hard with the current "simple" entry points; you'd actually need to modify the entry point based on the...
> Does editable mode do anything else to the importing other than adding stuff to sys.path ??? There are two editable modes. The inplace mode is simpler and does pretty...
Some of this might make it in the future. But can't you set this in your CMakeLists.txt?
We have an experimental hatchling plugin, you could try that if you want. The Python part of scikit-build-core is designed to look like hatchling, though we are currently missing "force-include"....
I ran into this on 1.11 with: ```python from typing import Any ruff: dict[str, Any] = {"src": ["src"], "other": True} match ruff: case {"src": ["src"]}: print("got it!") ``` It's fine...
I think the name of the new mode could be `editable.mode = "build-dir"`.