![playwright.png](https://images.hive.blog/DQmTv5HEmCZbqhtHN7C4jzh5dL8kPKjucRN7cy2Xp3voGow/playwright.png)

About a week ago I wrote about my switch from Selenium to Playwright as my preferred framework for automating web tasks. I am still impressed by Playwright and most likely continue using it. However, for a brief moment I was disappointed with Playwright when it was time to deploy the finished project to a Windows machine. The code simply didn't work at all. I was finally able to find a very easy solution, but not before I had to try everything else that involved a day of debugging, troubleshooting, uninstalling and reinstalling all relevant software and dependencies. In the end it turned out there was a simple solution that required adding a couple lines of code. I wish I saw this early on. I hope you won't go through trying different solutions, and use the simple one when you too face the same issue with Playwright.

My primary coding environment is Mac. Anything coding related I do on Mac, even if intended final destination for the scripts and apps would be Windowns. This project wasn't any different. The scripts I was rewriting in Playwright were due to overhaul in UI in the web app that automation tasks would be performed on. All of these scripts were intended to be used on Windows computers. When working with Selenium I didn't have compatibility issues running them on Mac and Windows. Apparently, Selenium is more Windows friendly than Playwright. Everything that worked perfectly on my Mac, stopped working when moved to Windows. This is because of the compatibility issues with asynchronous I/O operations in Windows environments when using Playwright and asyncio library.

In Windows, the default event loop used by asyncio was the SelectorEventLoop. However, this default loop has limitation with certain asynchronous I/O operations, especially involving pipes and subprocesses. The final solution I had to implement to make the scripts work was to add lines of code that would set the ProactorEventLoop as the event loop policy for Windows. The ProactorEventLoop supports asynchronous operations with Windows specific APIs, enabling proper handling of I/O tasks, such as subprocesses and pipes.

Before getting to this point, I had a few other options that required more coding. One of them was to forget about Playrwirght and rewrite everything in Selenium, because I certain I wouldn't have this issue with Selenium, because the old scripts worked just fine with the old UI. Another option was to rewrite all Playwright scripts utilizing asyncio. None of these were the ideal option because it would require dedicating a couple more days or a week just for the coding. The frustrating part was that I already had fully working and tested scripts. Maybe there was another soultions, maybe the problem wasn't the code but the software in the machines and dependencies. 

I uninstalled python and all used dependencies and software, and reinstalled everything. Maybe it was time to update everything. That created another issue of losing dependencies for other scripts that had nothing to do with this project. This added more work of identifying all needed dependencies and reinstalling them. Another issue was there were dependencies that only specific version was needed, and not the latest. I had to check and install all proper decencies for other scripts as well. All day was spent with figuring this all out and fixing all dependencies. In end everything was done, but the main problem wasn't solved. There had to be a simpler solutions, and there was. I almost gave up and was ready to postpone the project and rewrite everything in Selenium. I had to try one last solution, which turned out to be the one that fixed everything.

```
import asyncio
import sys
if sys.platform == "win32":
    asyncio.set_event_loop_policy(asyncio.WindowsProactorEventLoopPolicy())

```

That was it. After adding these couple lines of code everything worked as expected. I wish I knew about this solution before trying everything else. That said I have no regrets. There were benefits in these problem solving activities. That's the live working with codes. They don't always work as expected, but there are always solutions. Resolving these issues do bring sense of accomplishment as well. 

If you too face a similar issue when transferring Playwright code written and tested on Mac to Windows, hopefully search engines will lead you to this post and you can save time resolving the issue. Keep in mine the solution code lines above should be at the top of the script before everything else, even the import lines.