On Sun, 2016-05-08 at 07:07 +0100, Thomas Kluyver wrote:
> But you could run some tool beforehand that strips out comments and
> docstrings, renames variables, etc.
Stripping out comments/docstrings and asserts can be done by running
the code with 'python -OO'. I'm pretty sure I remember setting u
I have without problem created .exe with pyinstaller (python 2.7 + pygame).
Problem might be on how you import modules or defining paths to files. Have
you for eg. tried to run your project on different PC as code ? It might be
something simple that you have missed.
On Mon, May 9, 2016 at 4:50 AM,
If you had ALL your graphics, sound, fonts, libs and modules inside a
SINGLE EXEcutable would that help?
On Sun, May 8, 2016 at 11:37 AM, Thomas Kluyver wrote:
> Hi Scott,
>
> On 8 May 2016 at 06:00, scottmeup wrote:
>
>> I was hoping to obfuscate my code a little this time, do you know if this
I recall console=True working OK with my project - it opens the pygame window
of the application, plus an additional console window if the application is
started from the GUI. I don't think there's a fundamental problem using
console=True with pygame.
I haven't seen your code, so I don't know wh
Hi Scott,
On 8 May 2016 at 06:00, scottmeup wrote:
> I was hoping to obfuscate my code a little this time, do you know if this
> is
> a possibility?
>
Pynsist doesn't have any particular support for obfuscation. But you could
run some tool beforehand that strips out comments and docstrings, ren