-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any usage of poetry after installation: No module named 'tomli' #455
Comments
Hi @vwxyzjn I have to reopen this issue as I'm facing this again while attempting to execute the benchmarks for pr459 via Do you have any idea on how to debug this? I somehow managed to make it work on my local machine, which was sufficient to generate the pytoml and lock files. ppo_trxl.sh
|
Hey, I am also facing this issue on my institution's cluster. I also tried the Possible Solution by @MarcoMeter which unfortunately also results in the same error. Running: |
I believe I had more success with poetry when using the official installer. |
Problem Description
After installing the dependencies via poetry inside a conda environment, any use of poetry results in
ModuleNotFoundError: No module named 'tomli'
.Checklist
poetry install
(see CleanRL's installation guideline.Current Behavior
After creating a fresh conda environment, I run
pip install poetry
followed bypoetry install
. So far no errors are logged and it seems that the installation succeeded. But once poetry is used, likepoetry shell
orpoetry install -E docs
, the package tomli cannot be found even though its listed as completed during the first run ofpoetry install
.Expected Behavior
Open poetry shell or run any documented CleanRL process.
Possible Solution
cd cleanrl
conda create -n cl python=3.10 --yes
conda activate cl
pip install poetry
poetry shell
poetry install
poetry run python cleanrl/ppo.py
Steps to Reproduce
cd cleanrl
conda create -n cl python=3.10 --yes
conda activate cl
pip install poetry
poetry install
poetry shell
or any other poetry commandWhat I tried
The text was updated successfully, but these errors were encountered: