Question: Intended use with venvs #10
-
|
Hi,
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
(just enabled discussions, and transferred the issue 🙂)
The default setting is unset. The option is activated only if the value is 1. Any other value (0, empty, 2), and the venv feature will be disabled.
Definitely something to avoid indeed.
The idea is to declare and create a few venvs with PDM, then use the same names with PDM Multirun: # Unfortunately I don't think PDM supports creating multiple venv in the project folder,
# so we have to tell it to create them elsewhere. But maybe I'm wrong.
pdm config venv.in_project false
pdm venv create -n 38 python3.8
pdm venv create -n 39 python3.9
pdm venv create -n 310 python3.10
pdm venv create -n 311 python3.11
pdm venv create -n 312 python3.12
export PDM_MULTIRUN_VERSIONS="38 39 310 311 312"
export PDM_MULTIRUN_USE_VENVS=1
That's a good question. I started using PEP 582's
If neither 3.10 or 3.12 are listed in pyenv's global setting, then these two versions are actually not exposed in your PATH, and PDM can't find them. Therefore they are skipped when running PDM Multirun. My recommendation here is to add all your Python versions installed through pyenv to its global setting:
Yep, I think you always need to create the venvs first, because when you set By the way thanks for the one-time donation ❤️ 🚀 ! |
Beta Was this translation helpful? Give feedback.
-
|
That helped a lot! Just a quick thought about this... One could develop the #!/usr/bin/env bash
set -e
if ! command -v pdm &>/dev/null; then
if ! command -v pipx &>/dev/null; then
python3 -m pip install --user pipx
fi
pipx install pdm
fi
if ! pdm self list 2>/dev/null | grep -q pdm-multirun; then
pdm install --plugins
fi
if [ -n "${PDM_MULTIRUN_VERSIONS}" ]; then
if [ "${PDM_MULTIRUN_USE_VENVS}" = "1" ]; then
for version in $PDM_MULTIRUN_VERSIONS; do
if ! pdm venv --path $version &>/dev/null; then
pdm venv create --name $version $version
fi
done
preferred_version=$(pdm venv --path $PDM_PREFERRED_VERSION)
pdm use -f ${preferred_version}
fi
pdm multirun -v pdm install -G:all
else
pdm install -G:all
fiAdding to the export PDM_MULTIRUN_USE_VENVS = 1
export PDM_MULTIRUN_VERSIONS ?= 3.8 3.9 3.10 3.11 3.12
export PDM_PREFERRED_VERSION = 3.11To get the desired behavior (multiple venvs in Would that be s.th. you would like to see a PR in the copier-pdm repo for? |
Beta Was this translation helpful? Give feedback.
-
|
Yes! This is definitely something worth adding to the setup script 🙂 Great suggestion! To be clear, here's what I would accept:
And here's what I wouldn't accept:
|
Beta Was this translation helpful? Give feedback.
-
Sorry. 😄
Was too tired to say that yesterday: This really kicked the things off for my brain. Thanks!
Not sure.
I learned so much from your repos only in the last week, increasing my python (environment) skills a lot. This is the least I can do.
Guess this is not needed, as pdm seems to create external venvs for named venvs per default.
Great & clear communication from you 😍 and on second thought far more sensible (🧠 was tired yesterday...). Will see if I can manage a PR today, but feel free to take all ideas to your liking. And thanks for offering taking over the docs. |
Beta Was this translation helpful? Give feedback.
-
No, no, nothing to be sorry about, discussions weren't enabled when you opened the issue, you did nothing wrong.
That's probably because once PDM found each version once, it's able to find it again, even if it's not exposed in PATH anymore. PDM caches interpreters location in
The best thing I can read. It throws me back to when I myself learned a lot from someone else's Python template 😄 Nice, didn't know that! Learning from you too hehehe
Great, thanks! |
Beta Was this translation helpful? Give feedback.
(just enabled discussions, and transferred the issue 🙂)
The default setting is unset. The option is activated only if the value is 1. Any other value (0, empty, 2), and the venv feature will be disabled.
Definitely something to avoid indeed.
The idea is to declare and create a few venvs with PDM, then use the same names with PDM Multirun: