[GH-ISSUE #528] Pyinstaller takes 2 hours to build exe #406

Closed
opened 2026-02-26 12:21:30 +03:00 by kerem · 4 comments
Owner

Originally created by @Doccy-soft on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/528

I have a python app modules to build exe from them. It includes torch, tensorflow, and other heavy libs. I work in a virtual environment, but it takes >2 hours for pyinstaller to build the exe. The first-run and second run takes 5 seconds. I compiled bootloader manually to avoid false-positive issues.
What can I do to understand this behaviour?

Originally created by @Doccy-soft on GitHub (Apr 2, 2025). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/528 I have a python app modules to build exe from them. It includes torch, tensorflow, and other heavy libs. I work in a virtual environment, but it takes >2 hours for pyinstaller to build the exe. The first-run and second run takes 5 seconds. I compiled bootloader manually to avoid false-positive issues. What can I do to understand this behaviour?
kerem 2026-02-26 12:21:30 +03:00
  • closed this issue
  • added the
    Stale
    label
Author
Owner

@github-actions[bot] commented on GitHub (Apr 2, 2025):

👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.

Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.

<!-- gh-comment-id:2772000122 --> @github-actions[bot] commented on GitHub (Apr 2, 2025): 👋 Hi, just a reminder that if you haven't read [the help post](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/) yet, give it a read to see if your issue is covered in it and make sure to follow [the debugging section](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/#debugging). Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help [post](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/), [video](https://youtu.be/OZSZHmWSOeM) or create a [new discussion](https://github.com/brentvollebregt/auto-py-to-exe/discussions).
Author
Owner

@brentvollebregt commented on GitHub (Apr 2, 2025):

This will have to be a question for the pyinstaller team - I am unable to answer this sorry.

The reason the second build takes 5 seconds is because of the build cache.

<!-- gh-comment-id:2772217318 --> @brentvollebregt commented on GitHub (Apr 2, 2025): This will have to be a question for the [pyinstaller](https://github.com/pyinstaller/pyinstaller) team - I am unable to answer this sorry. The reason the second build takes 5 seconds is because of the build cache.
Author
Owner

@github-actions[bot] commented on GitHub (May 3, 2025):

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.

<!-- gh-comment-id:2848343287 --> @github-actions[bot] commented on GitHub (May 3, 2025): This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

Closing issue due to no activity in more than 60 days.

<!-- gh-comment-id:2861139122 --> @github-actions[bot] commented on GitHub (May 8, 2025): Closing issue due to no activity in more than 60 days.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/auto-py-to-exe#406
No description provided.