-
Notifications
You must be signed in to change notification settings - Fork 7k
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
installer breaks something. Causes a DeprecationWarning. (IDFGH-10465) #11712
Comments
We know about this and will be fixed soon. I don't think anything is broken. You can ignore that warning. Everything should work. |
This problem also occurs when doing a clean install of ESP-IDF release/v5.0 and release/v5.1.
|
Yes, the pkg_resources was used in all versions and was recently deprecated by the setuptools in version 67.5.0 |
So when we using setuptools older than 67.5.0, does the problem not occur? |
Yes, but it is not really a problem. It is just a warning message, it hasn't affected any functionallity of ESP-IDF even with newer setuptools. |
export.sh is switching to a different Python environment. So changing any package locally does not affect the IDF environment. If you care about the warning you can downgrade setuptools after running the export.sh as a temporary workaround until we implement a proper fix. We are already working on it and this issue will be fixed soon. |
i am waiting for a fix. |
@bbannert
|
@bbannert Which IDE are you using? Vscode or Eclipse? |
Answers checklist.
IDF version.
esp-idf-v5.2-dev-1128
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
What is the actual behavior?
I updated from esp-idf-v5.2-dev-544 to esp-idf-v5.2-dev-1128.
The following warning will occur:
So I changed it back to esp-idf-v5.2-dev-544.
esp-idf-v5.2-dev-1128's installer breaks something.
Steps to reproduce.
Build or installation Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: