e66b07e6fb
pyinstaller considers .py files to not be data by default. The entire architecture of pyinstaller is, in fact, different from zipapp or unpacked modules -- because it actually has to use a resource loader with on-disk files *separate* from the module itself. So just because a file gets packaged in the application does not mean it's usable as an importlib.resources compatible resource. Although we collect data files in general, we need to make sure that .py files are collected from scripts, because we may try to run them standalone from an external process. Fixes #11689 |
||
|---|---|---|
| .. | ||
| macpages/English.lproj | ||
| License.rtf | ||
| create_zipapp.py | ||
| createmsi.py | ||
| createpkg.py | ||
| hook-mesonbuild.py | ||