Only editable entry should trigger editable installs

[matteius]

Exploration of #6054

The checklist

• Associated issue
• A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

[edmorley]

Thank you for fixing this.

I notice no testcase was added - I feel like the current rate of regressions in pipenv releases is pretty high, and I'm not sure that will improve unless test coverage is also improved?

[matteius]

@edmorley if you look back on the issue that is still marked open, no one has responded to me when I ask for more details like what the difference even is between a editable and non editable local file install--

#6054 (comment)

I'm not opposed to adding test cases, however I think if you look you'll see I've added the most new test cases in the last two years, and the test runner used to take 45 minutes plus, now takes a fraction of the time, wasn't without a lot of hard effort. Yes the test runner needs more cases and more TLC, no I cannot be the one to ensure all those tests exist. I've refactored and simplified a lot of code in pipenv, and I often get caught by the lack of tests that already existed around original functionality folks expects. It is easy to ask for more tests, harder to implement them. I've spent hours at points trying to add tests for some things only to back them out for reasons due to the nature of trying to test some of this stuff.

[matteius]

Like I am not even convinced it is fixed, that is why I left the original issue open. But I thought this is a step on the path.