-
Notifications
You must be signed in to change notification settings - Fork 936
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
prepare support for Nuitka #2435
Conversation
@microsoft-github-policy-service agree |
@microsoft-github-policy-service agree |
happy to accept the changes in |
we need a way to know the paths of where the browsers are stored, nuitka would use this to determine the locations in order to bundle the browsers, if playwright isn't happy providing it directly from playwright itself, we could also patch it from nuitka ourselves, but it would make it far easier if it was within playwright already. |
We have the following workflow for Pyinstaller, that should also work for Nuitka?
If Nuitka isn't bundling all the files inside the site-modules directory, we recommend instead do do something like this:
I'm not a huge fan of |
we don't like affecting the user experience, so we generally just look wherever the program looks and go from there, this is in case the user runs from either an venv, or global packages, users don't normally set the |
another question, i see playwright downloads ffmpeg when you do a bare |
ffmpeg is needed for chromium based browsers in order to record video.
let's do that, then the Nuitka experience is on par with Pyinstaller. |
this PR will prepare playwright to make it easier to be compiled into standalone / onefile programs for ease of distribution
the following changes have been made:
in
playwright._impl._driver
, Nuitka will use this to resolve the path to the browsers ._compiled__
is in the globals dict, if it is, setPLAYWRIGHT_BROWSERS_PATH
to 0 just like for pyinstaller