Replies: 1 comment 2 replies
-
I eventually uninstalled poetry again in the test_poetry environment, tried pip uninstall poetry in the other environments, manually deleted all 'poetry' packages manually from "../../miniconda3/envs/manim_env/Lib/site-packages" and "../../miniconda3/envs/manim_env/conda-meta", "miniconda3\pkgs" and "AppData\Local\pypoetry". |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I don't know if this belongs here or in the issues page, but here goes.
I've been trying to find a way to get poetry to work in my environment, but I have been encountering more and more issues.
I had a previous almost empty conda environment called manim_poetry on which I installed using the online
curl -sSL https://install.python-poetry.org | python - (python3 doesn't work for my case, somehow)
Using the installation guide, I could not get my git repository from being able to be imported as a module.
So I uninstalled it, just to start from scratch, using the same script, and deleted the conda environment so that no traces were left.
I created a new empty conda environment called test_poetry, installed python on it, ran the installer and ran 'poetry env use python' as per https://realpython.com/dependency-management-python-poetry/ to maybe solve the issues. However, now I get these errors.
And I'm basically: "Yes. That python executable doesn't exist anymore, that's right." However, I can't run "poetry env use /path/to/actual_python.exe" since it gives the same error. (It uses python to set the python interpreter?)
Even after re-installing poetry again and creating another conda environment, this keeps happening. I also completely recloned the git repository from its starting state, so it is probably not that the pyproject.toml is bad. Any hints on how to continue? Or where to find the config file, so I can manually change this?
Beta Was this translation helpful? Give feedback.
All reactions