Randy Döring

There is already a core PR (python-poetry/poetry-core#520) with a corresponding change and a companion PR (#6844) to make sure that poetry still fails gracefully if a non-existent path dependency is...

There are even warnings about this in our test environment (which I have not attached much importance to so far): ``` tests/masonry/test_api.py::test_build_wheel_extended tests/masonry/builders/test_complete.py::test_wheel_c_extension tests/masonry/builders/test_complete.py::test_wheel_c_extension_src_layout C:\hostedtoolcache\windows\Python\3.11.1\x64\Lib\zipfile.py:1547: UserWarning: Duplicate name: 'extended/__init__.py' return...

I completely agree with dimbleby, but I may be in the minority among maintainers.

Since the implementation of `default` sources does not match the documentation (see #7430 for details) and changing the implementation so that sources configured as `default` do not have the highest...

In the last maintainer meeting we revisited the proposal, refined it and came up with a slightly differnt design alternative. I'll try to summarize it here, so we can decide...

While writing down the two approaches, I already had the feeling that the new proposal was too elaborate. Thanks for the confirmation. I think we will stick (more or less)...

Short status update: The first step is done: #7658 has been merged into master. Thus, the next minor version of Poetry will introduce explicit package sources, which are only searched...

> I don't really understand why this exception is only relevant to the `explicit` priority, but not to the `supplemental` one. It has a technical background. We need at least...

> Is that right? In principle, yes. Strictly speaking, it's not always the highest version but the highest version that fulfills all constraints. > I could imagine some people wish...

Your issue is not the resolver but the semantics of `poetry add`: IIRC `poetry add foo` is the same as `poetry add foo@latest`. What you expect is probably `poetry add...