-
Notifications
You must be signed in to change notification settings - Fork 21
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
Stopped working, says "ValueError: No Python Environment configured" #911
Comments
If it helps, this is the result of manually running a command I saw in the log:
And this is my requirements.txt file:
|
Did you try the steps in #899? |
I'm sorry, but I think this is beyond me. I inherited this system and am trying to understand this, but there does not seem to be one page with very clear steps to know how to install and debug this. This was all working perfectly a few days ago. I made no changes. The only thing I can think of is that one of the plugins that had the checkbox "auto update" may have updated and broken things. I am lost. I don't recall ever having to use github to create a repo for anything. I was hoping the log would at least give me a place to start. Also, when I was running without the venv in VSC, and then ran my batch file to create the venv, VSC used to popup a box saying something like "new virtual environment recognized, do you want to use it?". That doesn't happen anymore. |
Sorry, chances are I broke your workflow here 😅 I'm assuming that VSCode updated the Esbonio extension in the background which would have included a breaking change. (See 82c548e). Hopefully, all you need to do to get things working again is to set the {
"esbonio.sphinx.pythonCommand": ["C:\\Users\\Fred\\Documents\\PlatformIO\\Projects\\dcc-ex.github.io\\venv\\Scripts\\python.exe"]
} or wherever the batch file creates your virtual environment. Don't worry about the |
Can I do this from the gear settings on the Esbonio plugin? It seems to edit the VSC settings.json file when changes are made there. I tried changing the path, but it didn't work. I went back to the previous version and that fixed it. I agree with you that is must be the path if that is the only breaking change. When I look at what the "choose interpreter" says in the VSC "run commands" menu, it shows "Python 3.10.11 ('venv':venv) .\venv\Scripts\python.ext". And when I entered the path into your config screen, I could see that it entered a line like you showed above and the path looked correct. If there is something else you want me to try, I'm happy to do it. |
Yes either using the UI or editing the file itself should be fine.
When you say it didn't work, are you still seeing the If the config is being passed through correctly, I would expect you be able to see something like this
in the log output. |
Expected behavior
Expect Esbonio and its preview to works as it has. Nothing happens when I open the preview window at all except for the box saying "No content found"
Actual behavior
Preview windows says "no content found" and a popup in VSC says "ValueError: No Python Environment configured". I am using the same steps that have been working.
Windows 11, batch file creates a Venv and builds the website as usual. I go back into the run commands menu and deselect the python version and reselect it (my venv version) and restart the Esbonio server. It fills the log below. I could only upload a small percentage of the log because it is too long for github (greater than 65536 characters)
I did not update anything that I know of and am sure to run a requirements.txt file with the versions of everything I was using since the most recent versions of some things broke Esbonio. This is the only warning I see creating the venv and building the website (which builds correctly)
"WARNING: The candidate selected for download or install is a yanked version: 'requests' candidate (version 2.32.0 at https://files.pythonhosted.org/packages/24/e8/09e8d662a9675a4e4f5dd7a8e6127b463a091d2703ed931a64aa66d00065/requests-2.32.0-py3-none-any.whl (from https://pypi.org/simple/requests/) (requires-python:>=3.8))
Reason for being yanked: Yanked due to conflicts with CVE-2024-35195 mitigation". Log of Esbonio when I try to run it is below. Using v2024.17.2024100701 (pre-release) version of Microsoft's Python. I will try an older version. The release version did not work last time.
Log output
(Optional) Settings from conf.py
No response
The text was updated successfully, but these errors were encountered: