Description

Fixes #1123

I was figuring that the change to not record the editable for PyPI dependencies is quite easy, as we already knew no metadata changes between editable/non-editable. The change turned out to be pretty easy in the end and this just keeps the changes backwards compatible.

I think its safe to remove the satisfiability checks because we explicitly override the editable status before the installation. @baszalmstra what do you think?

So after this PR, we basically ignore the editable status for PyPI don't record it. Note, we do not remove the input hash just yet, we need this because the change to use the cached metadata will be more complex.

How Has This Been Tested?

I've manually user-tested this by changing editable/non-editable and checked if the lock file stayed identical and that the .pth file got added/removed.

Also ran all examples to see if these kept working, that's why the lock file changed, got an error for an unrelated reason. Also, I run all the automated tests, and added the reproducer for the issue.

Docker example

@pavelzw also changed your docker example and manually tested if these editable/non-editable was correctly installed.

AI Disclosure

• This PR contains AI-generated content.
  • I have tested any AI-generated content in my PR.
  • I take responsibility for any AI-generated content in my PR.

Tools: Opus 4.5

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added sufficient tests to cover my changes.
• I have verified that changes that would impact the JSON schema have been made in schema/model.py.