Closed amitkparekh closed 9 months ago
Hi!
That's weird cuz latest plugin version requires pdm~=2.10.0
, could you add to your pyproject.toml
the following lines?
[tool.pdm]
plugins = [
"pdm-conda>=0.14.1"
]
After that if you run pdm install --plugins
it should force pdm to use the correct plugin version
I'm just wondering, what does ~=
mean in this context? Could that be a reason, like PDM is downgrading to suit the plugin, but then some other Python break since PDM 2.6.1 might not support Python 3.11?
Oh you're using python 3.11, that's the problem, the plugin requires python~=3.10.0
, in this context ~=3.10.0
means >=3.10.0,<3.11.0
.
Let me see if changing the python requirement to python>=3.10.0
doesn't break tests
@amitkparekh this should be fixed on v0.14.2, if it doesn't please reach back
Hi! Something very odd happened.
I ran
pdm self add pdm-conda
and my PDM downgrades to 2.6.1, or maybe it claims to be 2.6.1? If I try to removepdm-conda
or try to update PDM (withpdm self update
), it says:This happened on my Mac (where I'm not running PDM within a conda environment), and within a Docker container on a linux machine (where I am running PDM within a conda environment). The only solution from this is to force re-install PDM.
Have you seen this before? Am I doing something wrong?