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
Binary built with PyInstaller doesn't recognize Python source file encoding in case the file doesn't have .py extension #8046
Comments
Is the entry point called Can we see the whole entry-point script? There seem to be at least 40 more lines to it, and one of it contains an non-ASCII character that likely triggers the issue... |
My bad, made a mistake in bug description. Here's correct spec part
|
If the entry point for frozen application is |
Updated Bug description one more time. Here's code for reproducing bug:
|
And if you freeze this script (presumably this is |
Sorry, updated Bug description once again. |
Does the error occur only if you run the program from |
I do copy aa-setup to another directory (not |
Okay, but it is reproducible only if the executable is in the current working directory, right? I think that happens because I think as a work-around, if entry-point script name has no suffix, we will add the .py to the name when compiling it. It is probably the least invasive way to take care of this... |
Binary built with PyInstaller doesn't recognize Python source file encoding in case the file doesn't have .py extension.
Context information (for bug reports)
pyinstaller --version
:6.0.0
PyInstaller command:
Spec file:
A minimal example program which shows the error
!!! Make sure that file name with the following code doesn't contain any extension (.py for example)
Stacktrace / full error message
Please also see https://github.com/pyinstaller/pyinstaller/wiki/How-to-Report-Bugs
for more about what would use to solve the issue.
The text was updated successfully, but these errors were encountered: