-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Poetry with WatchFiles - leads to a bug #7652
Comments
Most likely explanation is that poetry is installing the wrong binary. Please can you check which file is downloaded from pypi and installed with |
As a work around you should be able to set the |
feels like you've raised this too soon. If and when you discover a poetry bug, let us know! |
Hallo Samuel (& dimbleby), I am very sorry for this. Once again sorry for this. |
please close |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option) and have included the output below.Issue
Same is mentioned here (the "similar problem" mentioned later on the page).
WatchFiles is used as observer of file changes for FastApi+Uvicorn.
When I make the virtual environment using Poetry (and install fastapi + uvicorn[standard]), then
uvicorn --reload
is not able to run and fails.When I make "same" virtual environment using
python -m venv
andpip
, everything works well.I don't say it is an bug of poetry, however it would be good to investigate the problem more: install the "Hello world" example for FastApi+uvicorn and think a little why the internal Rust watcher fails - just in case when the virtual environment is created using poetry.
I don't believe that this is really "too many open files" problem. Because we are here with the "Hello world" application only. So probably the Rust watcher fails from another reason (when
poetry
handles the environment) and WachFiles reports bad message.The text was updated successfully, but these errors were encountered: