Closed fridex closed 1 year ago
Heya @fridex thanks for opening the issue, sounds like a bug to me ...
/kind bug /priority critical-urgent /assign @VannTen
If we accept the new scope proposed in #249 (point 1), this is out of scope. (because micropipenv should parse Pipfile.lock, not attempt to resolve Pipfile to Pipfile.lock)
If we accept the new scope proposed in #249 (point 1), this is out of scope. (because micropipenv should parse Pipfile.lock, not attempt to resolve Pipfile to Pipfile.lock)
This corresponds to the requirements feature. In some cases, users might want to convert Pipfile to requirements style output (see also pipenv requrements
command).
The reported bug affects micropipenv requirements --only-direct
in which case users want only direct dependencies converted to the requirements style file - hence Pipfile has to be parsed for that.
Ah, sorry - opened another issue.
Ideally yes, if there is only one standard for defining requirements and lockfiles, this would not be needed. But I would expect it will take some time (years?) to have the lockfile standard accepted and used widely. In the meantime, micropipenv could be helpful.
Does any of you plan to propose a fix for this bug?
Describe the bug
Given the following Pipfile:
Running the following command:
I get the following error:
Expected behavior
Requirements should be generated respecting VCS dependency stated in the provided Pipfile.