Paul Moore

## Use Case ### Description The project includes "script wrappers" defined in its metadata. ### In scope? No ### Discussion Script wrappers are the responsibility of the build backend to...

## Use Case ### Description The project metadata is changed. ### In scope? No. ### Discussion Project metadata changes should always require a reinstall, as they can fundamentally affect the...

## Use Case ### Description The project contains "compiled" native code, such as C or Rust components. ### In scope? No. ### Discussion When native source code is changed, a...

## Use Case ### Description The project contains a subpackage which is physically located outside of the package structure in the source tree. ### In scope? Yes. ### Discussion This...

## Use Case ## Description Assembling a package directory from separate parts in the source location (with the exception of the specific case discussed in the [previous comment](https://github.com/pfmoore/editables/issues/24#issuecomment-1623928959)). ## In...

Hi @abravalheri I actually think this is possibly simpler than you suggest - it looks basically like a simple case of having two different `pkgA` modules on `sys.path` - one...

Reopening as a reminder for myself. I do want to investigate this scenario more closely, and I think it's useful to have a discussion about import hooks and their limitations....

You may still have issues regarding (3), because the `json` file would need to be added to `sys.path` somewhere. To accurately match the "historical" behaviour here, maybe add an `__editable__..pth`...

I've been looking at this issue again. I'm trying to understand what the *actual* problem is with namespace packages. The root of my confusion is that basically, a top level...

I think @berdario is the only person who can do a new release, and he's not been very active here in quite a while. So I don't know if a...