previously made files with pyinstaller suddenly stopped working.

[MorrisNijland3]

hello,

About a month ago I made a file to handle json files, I used pyinstaller with wine on macos to make the exe file.
This file worked perfectly fine, but now suddenly after a month the file doesn't do anything.

If I make the file for macos, it still works. But even if I remake that file for windows, it won't work.

There were no changes made to the file.

Thank you.

[bwoodsend]

Its working a month ago doesn't really tell us anything. We need the error message and whatever code is used to locate and process these JSON files and the details of how you build your application.

[MorrisNijland3]

In that case, can you archive both the build and dist directory, and upload the archive somewhere so I can look at it? Could be that we end up collecting a Wine DLL somewhere, and that causes problems on real Windows (I recall putting in some checks against that some time ago, but it could be from a different codepath).

My sincere apologies for not responding due to medical reasons,

Here are the build and dist directory.
The first problem was not importing xlsxwriter, this problem is fixed if I'm right. Thank you very much.

https://mega.nz/folder/jAlW2RAa#CZ0APB_EA048VAuMttm81w

[rokm]

The first problem was not importing xlsxwriter, this problem is fixed if I'm right.

The problem seems to be that xlsxwriter is not packaged with the application:

>taken_overzicht.exe
Traceback (most recent call last):
  File "taken_overzicht.py", line 1, in <module>
ModuleNotFoundError: No module named 'xlsxwriter'
[2984] Failed to execute script 'taken_overzicht' due to unhandled exception!

You can aslo see

xlsxwriter MissingModule
imported by: taken_overzicht.py

in build\taken_overzicht\xref-taken_overzicht.html, which likely means that the module is missing from the python environment during the build.

[MorrisNijland3]

in build\taken_overzicht\xref-taken_overzicht.html, which likely means that the module is missing from the python environment during the build.

Which is weird, cause I explicitly used the environment with xlsxwriter and even used —hidden-imports. Why can’t xlsxwriter be imported while using the right env?
This is a part from pip3 list

scipy 1.10.1
setuptools 69.2.0
six 1.16.0
sniffio 1.3.1
stack-data 0.6.2
sympy 1.12
tensorboard 2.13.0
tensorboard-data-server 0.7.2
tensorflow 2.13.0
tensorflow-estimator 2.13.0
tensorflow-macos 2.13.0
termcolor 2.4.0
threadpoolctl 3.4.0
torch 2.2.2
torchaudio 2.2.2
torchvision 0.17.2
tornado 6.4
tqdm 4.66.2
traitlets 5.14.2
typing_extensions 4.11.0
urllib3 2.2.1
wcwidth 0.2.13
Werkzeug 3.0.2
wheel 0.43.0
wrapt 1.16.0
XlsxWriter 3.2.0
zipp 3.17.0

[rokm]

Which is weird, cause I explicitly used the environment with xlsxwriter and even used —hidden-imports.

If a module is not in the search path, no amount of hidden imports will help you...

Do you have multiple PyInstaller installations on your system? Are you running the one from this environment?

[rokm]

Also, if you use the latest PyInstaller release, it should print the search paths at the beginning of the build process. That should help you figure out what environment is actually in use.