-
Notifications
You must be signed in to change notification settings - Fork 25
pyinstaller does not put browser in exe file build #45
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
Comments
I tried to do this the file size has increased a little, but it still does not import the browser into the exe file
|
I came up with a temporary solution for this problem, maybe it will help someone who faced the same situation. The paths to the files may differ. Run your generated exe via CMD, and look at the path to the browser you need, and also check the path to your Python, and replace it with your own, for me it turned out like this: see your python folder here
see your browsers folder here
for me it turned out like this:
|
Ive spend some good amount of time trying to figure this out/debug this, but i could not get anything to work. Most likely some setup misconfiguration in the Playwright Registry. Contributions welcome! |
Probably requires adding a hook over https://pyinstaller.org/en/stable/hooks.html e.g. ~ https://github.com/pyinstaller/hooksample/blob/master/src/pyi_hooksample/__pyinstaller/hook-pyi_hooksample.py#L45 & https://github.com/pyinstaller/hooksample/blob/a2aabc4372ebf0f9c0f861f2cba2d6053f29c6b4/setup.cfg#L44 To include the browser executables |
i have a code:
this code works in visual studio code in venv
I try to create an exe file to execute it, but no matter what I enter in the terminal, it does not include the browser in the exe file, and therefore nothing works
I tried:
None of these methods work. Please , help me , when using the standard playwright in the code, the command from the manual works https://playwright.dev/python/docs/library
but the standard playwright does not allow logging into twitch
The text was updated successfully, but these errors were encountered: