fix: require Python 3.10+ in edict startup scripts#298
Merged
Conversation
4 tasks
This file contains hidden or 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
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.
Summary
start.shautomatically select a Python 3.10+ interpreterscripts/run_loop.shProblem
The repository README says Python 3.9+ is supported, and
start.shlaunches the dashboard with plainpython3. On macOS systems wherepython3is still 3.9, startup fails immediately because the codebase already uses Python 3.10+ syntax such aspathlib.Path | None.Fix
This PR aligns the startup path and docs with the real runtime requirement:
start.shnow looks forEDICT_PYTHON, thenpython3.12,python3.11,python3.10, and finallypython3, accepting the first interpreter that is 3.10+scripts/run_loop.shReproduction
On a machine with
python3 = 3.9.x, run:chmod +x start.sh && ./start.shStartup fails during import with:
Validation
http://127.0.0.1:7891/