You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it comes to binary packaging, we currently only support create a single, self-contained file.
While this is extremely convenient, it bares a performance penalty. PyInstaller bootloader needs to extract and copy all runtime dependencies every time the program launches. The directory it creates is deleted when the execution ends, expect for when the program crashes (killed). This also means that it might cause disk space problems.
To solve this problem, we can create a one-folder package, where the application code and the runtime dependencies are separated and packed into an archive.
This way, the executable itself is linked to a fixed dependencies directory, and the entire extract-and-copy process is not needed.
This does however means that users will have to unarchive the package, and run the executable from a fixed directory.
For this reason, we should maybe consider automatically providing an installation script that does the necessary unpacking and aliasing.
The text was updated successfully, but these errors were encountered:
iliapolo
added
feature
This issue introduces a new feature
minor
Implies this code change should bump the minor version of the project
labels
Aug 3, 2019
When it comes to binary packaging, we currently only support create a single, self-contained file.
While this is extremely convenient, it bares a performance penalty. PyInstaller bootloader needs to extract and copy all runtime dependencies every time the program launches. The directory it creates is deleted when the execution ends, expect for when the program crashes (killed). This also means that it might cause disk space problems.
To solve this problem, we can create a
one-folder
package, where the application code and the runtime dependencies are separated and packed into an archive.This way, the executable itself is linked to a fixed dependencies directory, and the entire extract-and-copy process is not needed.
This does however means that users will have to unarchive the package, and run the executable from a fixed directory.
For this reason, we should maybe consider automatically providing an installation script that does the necessary unpacking and aliasing.
The text was updated successfully, but these errors were encountered: