Replies: 1 comment 1 reply
-
It is homebrew's fault to put a version in the path, isn't it? For PDM installed by the install script, it should be The only varying part is the python version |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is it possible to create a workflow for using a version agnostic pep582 initialisation path?
I'm referring to the
pep582
script which gets injected to.zshrc
(Mac)When upgrading PDM via
brew
the new version number invalidates the existing script path, e.g.1.14.1
would render this path useless whenpdm
is next updated.Is there a way to create a version agnostic path so that we don't need to manually update the configs?
EDIT - I guess the same is true for the
.pdm.toml
file, which means that each time brew updatespdm
we need to check thatpdm.toml
files are pointing to the latest version?Beta Was this translation helpful? Give feedback.
All reactions