Yes, Kregan. I did solve the issue per Brenainn's successive recommendations—the first one (numpy.f2py) with the --collect-submodules=, and the other ones with the --hiddenimport=, though I found that all the three could be collected with the --collect-submodules=. By the way, installing pytest in the venv aids in properly collecting the numpy.f2py as pyinstaller recommends. Thanks and regards, Debabrata
On Thursday, July 4, 2024 at 1:08:42 AM UTC+5:30 Kergan Sanderson wrote: > My previous post was all in the context of macOS. I ran PyInstaller on my > Windows machine that DID NOT have the latest versions of SciPy or Numpy and > the executable ran fine. > > When I reinstalled my venv on my Windows machine to update to the newest > versions of all my packages (including numpy 2.0.0 and the latest scipy), > pyinstaller ran, but the executable didn't work. It gave me the same errors > as I had on my mac. By running the same PyInstaller command that I had used > on my mac (with the / replaced by \ because of Windows), PyInstaller > worked, but the executable still had an error. > > It seems that Numpy 2.0.0 and/or SciPy 1.14.0 both are slightly > problematic with PyInstaller. Both had new versions released within the > past month, which is likely why Debabrata and I have the same issue at the > same time. > > MY RECOMMENDATION: use NumPy v1.26.4 and SciPy v1.13.1 instead of the > latest releases. After I uninstalled the latest and installed these two, my > Windows and macOS PyInstallers were able to work with no extra > --collect-submodules= pieces in the command. > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pyinstaller/5904f375-631d-40c7-98b7-d282a2caaaa5n%40googlegroups.com.
