Skip to content
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

Feature: Extended Windows support #731

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

aleezanooor
Copy link

Hi exo team,

I’m thrilled to contribute to the exo project because I genuinely love what you’re building—a powerful, open-source platform that brings people together. This pull request extends Windows support to make the project more accessible to Windows users like me, and I hope it helps grow the community even further!

What’s Changed
To make exo play nicely on Windows, I’ve made the following updates:

  • Updated Dependencies: Replaced the Linux-specific uv loop with its Windows-compatible counterpart to ensure smooth event handling on Windows.
  • Tinygrad Compatibility: Tweaked the tinygrad library for Windows 11 Pro by adjusting platform-specific calls, making it fully functional for Windows users.

Why It Matters
This opens exo to the Windows ecosystem, broadening its accessibility. I’ve tested everything on Microsoft Windows 11 Pro to ensure it’s rock-solid.

Testing

  • Ran the updated code on Windows [version] to verify the uv loop replacement handles [specific tasks, e.g., async operations] correctly.
  • Validated tinygrad functionality with the browser ui to ensure it performs consistently.

Notes
First-time contributor—happy to refine anything you suggest!

Thanks for taking a look, and for all the amazing work you do with exo. Can’t wait to hear your feedback!

Cheers,
Mohammed Salman (aleezanooor)

@tensorsofthewall
Copy link
Contributor

tensorsofthewall commented Mar 1, 2025

I suggest not using netifaces since its unmaintained (archived project), and causes installation issues on Windows/wsl. #607 replaces it with scapy, i would suggest sticking to that, or using a different library thats well maintained.

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.

2 participants