If you really want to learn about obfuscating python bytecode so it can't
be reverse engineered (easily) -- there are people who are doing it.
Search for 'pyasm' on github as a starting point. tldr; yes people are
patching .pyc files. yes you can make them a nightmare to disassemble. and
yes it sl
On Wednesday 16 March 2016 05:59, Thomas 'PointedEars' Lahn wrote:
> On a more constructive note, python(1) (CPython) creates a binary (byte-
> code) “.pyc” file from “.py” files when it runs them.
To be precise, it creates a .pyc file when the file is imported, not run.
Just running a Python
Chris Angelico wrote:
> On Wed, Mar 16, 2016 at 5:59 AM, Thomas 'PointedEars' Lahn
> wrote:
>> That said, not distributing the source code of a program as well (or at
>> least making it available to users in some way) strikes me as unpythonic
>> since Python is at least Open Source software, and
On Wed, Mar 16, 2016 at 5:59 AM, Thomas 'PointedEars' Lahn
wrote:
> That said, not distributing the source code of a program as well (or at
> least making it available to users in some way) strikes me as unpythonic
> since Python is at least Open Source software, and Python 2.0.1, 2.1.1 and
> newe
Ben Finney wrote:
> Swanand Pashankar writes:
>> Embedding a Python file in C code works, but it exposes your Python
>> script. Didn't find any free fool-proof way to obfuscate Python code
>> either.
>
> What exactly is it you want to prevent? Why do you think obfuscating the
> code will achieve
Swanand Pashankar writes:
> Embedding a Python file in C code works, but it exposes your Python
> script. Didn't find any free fool-proof way to obfuscate Python code
> either.
What exactly is it you want to prevent? Why do you think obfuscating the
code will achieve that?
--
\ “The int
