aboutsummaryrefslogtreecommitdiffstats
path: root/examples/webenginequick
diff options
context:
space:
mode:
authorChristian Tismer <tismer@stackless.com>2021-07-22 11:49:25 +0200
committerChristian Tismer <tismer@stackless.com>2021-07-28 18:41:46 +0200
commit45a8fafb9c445ebcdea125b0c20cd14dc42784d1 (patch)
tree386c41e804e557789d8e0c3b8c6c4ab8f86c3d9c /examples/webenginequick
parent9b5fa60d1fed5025e97c393ba1bab80f81ba833a (diff)
Remove signature loader completely from physical FS
This proposal was discussed. It was also tested with Nuitka and cx_freeze. [ChangeLog][shiboken6] Python support files are now always embedded. There is no longer a physical copy installed in the FS. Reasoning is: We always had the signature module in real Python files and also as an embedded ZIP file. With the solution to PYSIDE-1621 we suddenly had a way to avoid accessing the file system completely. The remaining question is: Why should we keep the files in the installation at all? Long time ago, it was said that the source files were needed to see tracebacks. But tracebacks are visible the same way, regardless if the files exist as physical files or only in memory. The error messages will be as verbose as always. Personally, I see it more as a drawback, because parts of our application become vulnerable by external manipulation. By the complete virtualization, the system is as self-contained as a binary executable. Task-number: PYSIDE-1621 Change-Id: I821545fb5d52465b69bb2c172bdfb43894ac2109 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'examples/webenginequick')
0 files changed, 0 insertions, 0 deletions