Skip to content

Fix windows python path issue #218

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

Merged
merged 5 commits into from
Jul 8, 2025
Merged

Fix windows python path issue #218

merged 5 commits into from
Jul 8, 2025

Conversation

Jason2866
Copy link

@Jason2866 Jason2866 commented Jul 8, 2025

Description:

by setting the PYTHONPATH env variable with the Platformio (virtual) Python path

Checklist:

  • The pull request is done against the latest develop branch
  • Only relevant files were touched
  • Only one feature/fix was added per PR, more changes are allowed when changing boards.json
  • I accept the CLA

Summary by CodeRabbit

  • New Features

    • Improved Python dependency management with dynamic environment setup for reliable package discovery.
    • Enhanced installation process for required tools, providing clearer success or failure feedback.
  • Documentation

    • Added comprehensive docstrings to multiple functions, detailing arguments, return values, and behavior for better clarity.

Copy link

coderabbitai bot commented Jul 8, 2025

"""

Walkthrough

The update centralizes Python dependency definitions, introduces functions to dynamically configure PYTHONPATH and sys.path based on the active Python environment, and ensures subprocesses inherit these settings. Dependency installation and package checks are improved for robustness. Comprehensive docstrings with argument and return type annotations are added throughout the codebase.

Changes

File(s) Change Summary
builder/main.py Centralized Python dependencies; added add_to_pythonpath and setup_python_paths; improved subprocess env setup; enhanced install_python_deps and install_esptool to use updated environment and return bool; added internal _get_installed_uv_packages; moved install calls; added detailed docstrings to many functions; updated firmware_metrics to use new env.

Poem

🐇
In the warren of code, new paths appear,
Python’s trails made crystal clear.
With docstrings bright and envs aligned,
Dependencies found, no bugs to find.
A hop, a skip, the builder’s delight—
Everything’s ready, and all set right!

"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f889426 and 68c62ff.

📒 Files selected for processing (1)
  • builder/main.py (23 hunks)
🧰 Additional context used
🧠 Learnings (1)
builder/main.py (1)
Learnt from: Jason2866
PR: pioarduino/platform-espressif32#199
File: builder/main.py:221-226
Timestamp: 2025-06-26T09:55:55.788Z
Learning: In the _update_max_upload_size function in builder/main.py, the `sizes` variable that maps partition subtypes to their sizes should not be removed despite appearing unused to static analysis tools. The variable serves a purpose that's not immediately obvious from the code structure.
🔇 Additional comments (7)
builder/main.py (7)

38-47: LGTM: Well-structured dependency centralization.

The centralized python_deps dictionary improves maintainability by consolidating all Python dependencies with their version specifications in one location.


59-81: LGTM: Previous path normalization issue has been resolved.

The function correctly normalizes both the new path and existing paths before comparison, preventing duplicate entries with different path representations. This addresses the previous review feedback effectively.


83-122: Robust Python path setup with comprehensive fallback handling.

The function effectively handles various edge cases:

  • Validates Python executable existence
  • Uses subprocess with timeout for site-packages discovery
  • Provides fallback paths for both Windows and Unix systems
  • Includes proper error handling for subprocess failures

This should resolve Windows Python path issues by dynamically configuring paths based on the actual Python executable.


147-268: Enhanced dependency installation with improved error handling.

The function improvements include:

  • Better timeout handling (30 seconds)
  • Proper environment propagation via env=os.environ
  • Comprehensive error messages
  • Boolean return values for success/failure tracking

The nested _get_installed_uv_packages function is well-implemented with proper JSON parsing and error handling.


855-856: LGTM: Environment propagation for esp-idf-size.

The subprocess call correctly uses env=os.environ to ensure the modified PYTHONPATH is available to the esp-idf-size tool.


312-870: Comprehensive docstring enhancements improve code maintainability.

The addition of detailed docstrings with argument and return type annotations significantly improves code documentation. All functions now have clear descriptions of their purpose, parameters, and return values.


124-124: Early Python path setup ensures proper environment configuration.

Calling setup_python_paths(env) early in the script ensures that the Python environment is properly configured before any subprocess calls or dependency installations occur.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Jason2866
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Jul 8, 2025

✅ Actions performed

Full review triggered.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f889426 and d059a6b.

📒 Files selected for processing (1)
  • builder/main.py (23 hunks)
🧰 Additional context used
🧠 Learnings (1)
builder/main.py (1)
Learnt from: Jason2866
PR: pioarduino/platform-espressif32#199
File: builder/main.py:221-226
Timestamp: 2025-06-26T09:55:55.788Z
Learning: In the _update_max_upload_size function in builder/main.py, the `sizes` variable that maps partition subtypes to their sizes should not be removed despite appearing unused to static analysis tools. The variable serves a purpose that's not immediately obvious from the code structure.
🔇 Additional comments (6)
builder/main.py (6)

38-47: Good centralization of Python dependencies.

The centralized dictionary makes dependency management cleaner and more maintainable.


82-121: Well-designed Python path setup with robust fallbacks.

The function properly handles different scenarios:

  • Queries the actual Python executable for site-packages location
  • Provides platform-specific fallback paths
  • Includes appropriate error handling

This approach should effectively resolve the Windows Python path issues mentioned in the PR objectives.


171-172: Correct propagation of environment variables to subprocesses.

The consistent use of env=os.environ ensures that all subprocess calls inherit the modified PYTHONPATH, which is essential for resolving the Windows Python path issues.

Also applies to: 204-205, 247-248


280-285: Consistent environment propagation in esptool installation.

The function correctly passes the modified environment to subprocess calls, maintaining consistency with the overall fix.

Also applies to: 297-297


854-855: Environment correctly propagated to esp-idf-size subprocess.

The modification ensures that the esp-idf-size tool runs with the correct Python environment, completing the fix for Windows Python path issues.


126-136: Excellent documentation improvements throughout the codebase.

The comprehensive docstrings with argument and return type annotations significantly improve code maintainability and readability.

Also applies to: 147-152, 270-278, 311-320, 336-345, 362-371, 376-385, 390-399, 407-416, 425-433, 444-453, 462-471, 484-493, 537-547, 583-591, 595-602, 631-642, 647-653, 803-812

@Jason2866
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Jul 8, 2025

✅ Actions performed

Full review triggered.

@Jason2866 Jason2866 merged commit ab68ffd into develop Jul 8, 2025
66 checks passed
@Jason2866 Jason2866 deleted the poc_python_windows_fix branch July 9, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant