mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-26 04:05:49 +03:00
[GH-ISSUE #71] How to create a standalone python executable with pymc3 package? #69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dvimal27 on GitHub (Sep 20, 2019).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/71
I have created a mathematical model in python. I want to make a standalone python executable for my model. The python script uses several python libraries like numpy, pandas, pymc3. I tried to make a python executable using pyinstaller and also auto-py-to-exe. In both cases, it failed to create the executable. The error occurs while importing the pymc3 module (theano library). My primary model is dependent on pymc3 module. I cannot bypass this module. Could anyone please help me to sort out this issue?
Here is the error message I get when I execute the .exe file,
Here is the python script,
@brentvollebregt commented on GitHub (Sep 20, 2019):
Did you read my post on Issues When Using auto-py-to-exe? This is linked at the bottom of the UI after every build and in the README of this repository; I highly recommend you give it a read.
In the post I discuss the error of modules not being found. This is very similar to your issue here so you could try to add
scipyas a hidden import.Also is this actually an issue with auto-py-to-exe? I can't seem to see anything directly wrong with the tool here.
@dvimal27 commented on GitHub (Sep 23, 2019):
Thank you.
I've added scipy as hidden import. But, still the same issue persists.
@brentvollebregt commented on GitHub (Sep 23, 2019):
Is it the exact same error? If so, are there any warnings regarding scipy in the build output?
You should be able to copy the PyInstaller command that is being executed from the UI. When executing it, do you get the same results?
@dvimal27 commented on GitHub (Sep 23, 2019):
Yeah. It's the same error.
@brentvollebregt commented on GitHub (Sep 24, 2019):
Ok, and my other questions? Warnings? When executing the pyinstaller command, do you get the same result?
@dvimal27 commented on GitHub (Sep 24, 2019):
I get the same result.
Here is the error message, when I run the .exe file
Here is the Output from Pyinstaller UI,
@brentvollebregt commented on GitHub (Sep 24, 2019):
Awesome, then the question I asked in my first reply is now answered: this is not an issue with auto-py-to-exe. This is on pyinstallers side.
If you wish, you can report this as an issue on pyinstallers GitHub repo.
@dvimal27 commented on GitHub (Sep 24, 2019):
Okay. But, how do I resolve the issue? Any suggestions?
@brentvollebregt commented on GitHub (Sep 24, 2019):
Did you search for the error and do some research? Looks like pyinstaller/pyinstaller#1713 and this comment discuss similar issues with solutions.
@dvimal27 commented on GitHub (Sep 25, 2019):
Thank you.
Now, I could get rid of the import issues. But now there is some issue with compilation. Could you please help me in this regard?
Here is the error message from .exe
@brentvollebregt commented on GitHub (Sep 26, 2019):
Please see pyinstaller/pyinstaller#2512 and the related pyinstaller/pyinstaller#2114 issue. This is not an
auto-py-to-exeissue and is not apyinstallereither as described by htgoebel.