Diez B. Roggisch wrote:
> Sreejith K wrote:
>> So I compiled Python from source changing some opcode values
> Nobody
> can be helping you there, because it's *your* code, not Python anymore.
> And giving others access to it defies somewhat the purpose of the whole
> exercise
...and everyon
Sreejith K wrote:
I know this is not the best way to do it. But I have to do it at least
to make it *hard* to decompile the python bytecode.
So I compiled Python from source changing some opcode values
It probably wouldn't be all that hard for someone to
figure this out. A possible avenue of a
Sreejith K wrote:
> On Aug 18, 12:19 pm, "Diez B. Roggisch" wrote:
>
>> Did you try installing the egg *without* pyc-files in there? Because
>> naturally those shouldn't work. They shouldn't crash the interpreter
>> either, but then again - you *did* modify it.
>
> Hi Diez, thanks for the immed
On Aug 18, 12:19 pm, "Diez B. Roggisch" wrote:
> Did you try installing the egg *without* pyc-files in there? Because
> naturally those shouldn't work. They shouldn't crash the interpreter
> either, but then again - you *did* modify it.
Hi Diez, thanks for the immediate reply :)
I installed the
Sreejith K schrieb:
Hi,
I know this is not the best way to do it. But I have to do it at least
to make it *hard* to decompile the python bytecode.
I want to distribute a software written in Python without the source.
So I compiled Python from source changing some opcode values (Taking
care of H
Hi,
I know this is not the best way to do it. But I have to do it at least
to make it *hard* to decompile the python bytecode.
I want to distribute a software written in Python without the source.
So I compiled Python from source changing some opcode values (Taking
care of HAVE_ARGUMENT value) an