So far as the code change goes I'm basically reviewing my own suggestion here. Looks fine to me, but this is not an independent review.

I think I would have expected to write a testcase here that more closely follows the actual problem as laid out in the issue report. Probably something in test_installer.py that sets things up and runs poetry install and checks that the expected thing happens.

I always find those testcases unpleasant to write, which is partly what put me off doing anything with this one in the first place. If you can convince yourself - and someone with the commit bit - that what you have is sufficient, then your life will be easier.

I added a test, LMK if that's what you were looking for ;)

I added a solver test. There is some overlap with the installer test, but since it's not (only) an installer issue but first of all a solver issue (i.e. the package with the explicit source is not only not installed but not locked), it made sense to me.

Now, we should have more than sufficient test coverage. 😀

Deploy preview for website ready!

✅ Preview
https://website-1pp39wxs6-python-poetry.vercel.app

Built with commit 42364f1.
This pull request is being automatically deployed with vercel-action

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.