You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm struggling to figure out how to do this:
In dependencies, we have a common library in prod.
In our flow:
We remove pdm lock and .venv so these files can be completely clean.
To successfully run pdm install, we need PDM to skip looking at the prod version and get the dev version of this library (a local editable), and so we remove common, run the install, and then add it back in.
Goal: Avoid having to edit the .toml every time we want to create a new lock file / venv
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm struggling to figure out how to do this:
In dependencies, we have a common library in prod.
In our flow:
pdm install
, we need PDM to skip looking at the prod version and get the dev version of this library (a local editable), and so we removecommon
, run the install, and then add it back in.Goal: Avoid having to edit the .toml every time we want to create a new lock file / venv
Is there any way to avoid this?
I've been looking into this solution but don't know how it would be formatted:
https://pdm-project.org/en/latest/usage/dependency/#dependency-overrides
Beta Was this translation helpful? Give feedback.
All reactions