-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pdm remove will raise PdmUsageError when spliting prod and dev dependencies in different lockfiles. #3404
Comments
I tried it on optional-dependencies ( |
I can reproduce what you have said. But from my point of view, optional dependencies are different from dev dependencies. Have you tried the dev dependencies approach as I mentioned in the |
Yes, I mean that maybe you could observe how this procedure runs in optional-dependecies, and see whether dev dependencies could refer to this procedure to fix this issue. Just a debugging suggestion. |
Seems the issue is caused by @frostming, Do you have any suggestions on this? [1] Line 79 in 564d09a
[2] Line 89 in 564d09a
|
Describe the bug
I tried to maintain two lockfiles, one
pdm.lock
is for prod dependencies and the otherpdm.dev.lock
is for dev dependencies. So onlydefault
group is in thepdm.lock
.When trying to remove a prod dependency with
pdm remove -v <package>
, the remove functionality works, but pdm will complain about the following error:To reproduce
Expected Behavior
pdm remove should work with no error
Environment Information
Verbose Command Output
Additional Context
I tried to debug into the code, the traceback is something like following:
Seems it is caused by the
sync
operation in remove, I wonder what is the recommend approach to solve this problem, I may try to submit a pull request to fix it.Are you willing to submit a PR to fix this bug?
The text was updated successfully, but these errors were encountered: