Paul Moore

I guess one solution for you is to simply implement your own editable install hook, that makes the trade-offs that suit your requirements. That was always the intention for editable...

> What command do you mean by "build"? https://pypi.org/project/build/ That's the build tool recommended in [the tutorial](https://packaging.python.org/tutorials/packaging-projects/#generating-distribution-archives).

Please add documentation to the PR that explains how this would be used in practice. I'm not committing to accepting this idea at this point, but a prerequisite for considering...

I don't particularly understand the logic behind the "essential layout" - there's no `pyproject.toml` shown in the layouts described, so I don't see the full picture here. But I think...

No, the `__init__.py` is added to `ns/pkgA`, not to `ns`. ``` >>> from editables import EditableProject >>> my_project = EditableProject("foo", "/path/to/foo") >>> my_project.add_to_subpackage("ns.pkgA", "src/pkgA") >>> list(my_project.files()) [('foo.pth', ''), ('ns/pkgA/__init__.py', "__path__...

Hmm, that's a good point. And the approach of reading and executing `__init__.py` in the generated one is a plausible fix. But what I really need here are some good,...

It sounds to me like `prepare_metadata_for_build_wheel` might be returning a different version than `build_wheel` - which could be because the version is based on a time (the resolver can take...

I feel as though the best option might be to deprecate multiple use of `--platform`, so that users would just run a `pip download` command for each platform. The resolver...

> My concern is either it was implemented the way it was because there's some important use case that's been forgotten My point is that if it currently doesn't work,...

Ah, OK. I interpreted the OP's description as "any use of `--platform` after the first is ignored" (and I was advocating deprecating extra uses, rather than silently ignoring them). Apologies...