Randy Döring

> Would you accept a PR add a section about them? I do not see why we should not. 😃

> if all of the path dependencies are PEP-517 dependencies then assume that the build backend is deterministic I suppose with "PEP-517 dependencies" you are referring to projects that declare...

> Any options for moving forward? This is definitely not on my priority list. If you are interested in implementing it, you have two options: - Discuss the exact design...

I do not have a strong opinion, just some thoughts: 1. It is not easy to know if a change will affect the export plugin. When I remember my PRs...

In my opinion that makes sense. We should pay attention to the following details: - There should not be a difference for the different repository types. If we decide that...

> Is it not easier to extend cache logic to clear specific packages You can clear specific versions of a package. See the docs: https://python-poetry.org/docs/cli/#cache-clear

> what is the officially suggested solution / workaround? Especially in CI, you can work around this issue by just installing the required plugins explicitly instead of relying on `requires-plugins`....

> It's been a known issue for 5 months now and entails some fragile/undesirable workarounds. In my opinion, the workarounds are pretty decent. Before Poetry 2 there was no `requires-plugins`,...

I read through the comments and think with the current information, it is difficult to formalize concrete acceptance criteria other than "it works". The most useful information about the issue...

> So existing dependencies can be constrained but new dependencies cannot be inserted (or at least not pip). This is expected because: > implemented as dependencies of an optional group,...