Pin littlefs-python requirement for older versions of Python #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to ESP-IDF v5.0 and v5.1 supporting Python 3.7 Related jrast/littlefs-python#78
|
looks good to me! will merge and tag a release. Thanks! |
|
released in v1.14.2 |
|
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi again.
We finally got to merge backports of LittleFS example in ESP-IDF to v5.0 and v5.1 branches but the CI is broken again... Due to me not fully understanding virtual environments in Python. However this change should fix it. ESP-IDF v5.0 and v5.1 has minimal version requirement for Python to be 3.7 so we released
littlefs-pythonversion 0.9.3 (jrast/littlefs-python#78) while ago (it seems 0.10.0 should also be compatible) and this change should make sure the virtual environment created during fetchingjoltwallet/littlefs(esp_littlefs) from component manager will have the exact version we need.@BrianPugh
Thank you.