Sergei Iakhnitskii

> The problem is your use of `--config`. Using `--config` means we have to use the current working directory as the root for resolving relative paths. Thanks for the investigation....

> The original example you provided works because we discover the workspace root by discovering the `pyproject.toml` on disk in the parent directory. That's the intended setup -- can you...

> If you use configuration on-disk, rather than passing `--config`, the calls will _always_ yield the same results regardless of the current working directory. It's the most robust way to...

> Can you explain you expect something other than the result you showed above? You marked them as being part of the same section. I expect ruff do not change...

If `module.py` was outside of `library` (and `plugins`) it would be right to receive the second snippet.

> But you have: > > ```toml > appnexus = [ > "library", > "plugins", > ] > ``` > > And so imports of `library` and `plugins` are being...

> If you have: > > ``` > appnexus = [ > "library", > "plugins", > ] > ``` > > Then any imports of modules named `library` or `plugins`...

> I think in that case you'd want to omit `library` from `appnexus`, since you want library imports to be considered first-party? It is `appnexus` for the whole project, but...

> Right now I use pathlib and tomlkit to emulate this feature by generating pyproject.toml programmatically. And pyproject.toml is several thousand lines long. Hi! Listing all packages manually as a...

[Providing macOS SDK](https://github.com/astral-sh/ruff/issues/5226#issuecomment-1603652378) helped, but is it the only way to cross-compile jemalloc?