Fixed editable package with markers can not be locked

[jxltom]

The issue

Fixed #2902 and also added tests. Without this patch, the new added test will fail.

The fix

Fixed in upstream sarugaku/requirementslib#71. If it can be accepted in upstream, then it can be merged here.

The checklist

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

[uranusjr]

I think this can be closed? We upgrade vendor packages before release. The fix in RequirementsLib will be included by the automated script, so you don’t need to do this manually.

[jxltom]

No problem.

But how about the added tests? It will be nice to have tests which can make sure that later development won't break any current working cases

[uranusjr]

I’d be fine if there is a test to ensure pipenv lock -r works, so I’ll merge if you take out the requirementslib patch (and probably change the news fragment). We’ll need to do it later though, otherwise it’ll break all CI.

[jxltom]

Great.

I've udpated the PR which removed the requirementslib patch as well as the news (since the test is too trivial)

Currently the CI would be broken but it should be fine after sarugaku/requirementslib#71 is merged from upstream.

[techalchemy]

I’ll release requirementslib in the next few days when I am sure we captured everything

[jxltom]

Update: it's ready for merge since #2935 has been merged