io.BytesIO as modules to Pyinstaller.__main__.run() #5594
farnking
started this conversation in
Features & Development
Replies: 1 comment 1 reply
-
Well it certainly should be but isn't. Even our own test suite is resorts to temporary files. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, dear Sirs:
I am developing a tool in python and would like to see whether we can use io.BytesIO or io.StringsIO as modules to Pyinstaller.main.run().
The motivation is protecting my IP and in the same time maintain the portability of our tool across platforms.
To make the download cross-platform, our server may send pyc bits to the clients, then convert those pyc files-in-memory to pyd files-in-memory, and then finally use pyinstaller to package everything to EXE with a desktop icon.
In this way, all the pyc and py files downloaded from our server only stay in memory without a trace in the clients' disks.
We feel this is the best way to protect our IP with your pyinstaller and python.
Moreover, we don't have to worry about the generation of native machine code in our server side.
But all the related pages in the internet only show how to use pyinstaller.main.run() for using py (or maybe pyc) files in disks as modules.
In this way, my tool pyc file may be copied in the clients' folder and decompiled for the source python program of my tool.
It is said that decompiling pyc files is much easier than decompiling their pyd counterparts.
Thus I am curious if it is possible to run pyinstaller.main.run() with io.stringsIO or io.bytesIO as the source modules.
Thanks
Farn
Beta Was this translation helpful? Give feedback.
All reactions