-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Pyinstaller import #63
Comments
Putting Are you using |
Ohhh interesting. I just added the The issue was fixed with the hidden-import argument, so honestly I'm probably not going to test it without it at the moment. In the future when I have more free time I'll give it a test. And correct, I'm using Thanks for the information! I'm not really sure how to deal with this post, as it's not an issue, but I thought it was worth sharing for someone who might experience a similar problem in the future. Thoughts? |
Right, so because imageio does not explicitly import It's indeed not technically a bug, but a good question nonetheless. I'm going to close it, and maybe Google will find it when someone with a similar question comes along :) |
Commenting to note that indeed, adding the |
Hello,
I've built an application using pyinstaller that relies on imageio-ffmpeg for movie creation.
When freezing the application in a non-windowed manner, I was having no issue with writing movies. However, when building a -windowed application on macOS, I was getting an import error telling me that the writer couldn't establish a link to the file path.
I found that this issue could be simply solved by adding the following argument to a build command:
--hidden-import=imagio-ffmpeg
I wasn't sure where else to report this, but I figured I would share it here for any help.
I'm using
pyinstaller==4.3
andimagio-ffmpeg==0.4.3
The text was updated successfully, but these errors were encountered: