obviscating python code for distribution

[Littlefield, Tyler]

I'm putting lots of work into this. I would rather not have some script 
kiddy dig through it, yank out chunks and do whatever he wants. I just 
want to distribute the program as-is, not distribute it and leave it 
open to being hacked.
On 5/15/2011 9:29 PM, Ben Finney wrote:
> "Littlefield, Tyler"<tyler at tysdomain.com>  writes:
>
>> I have been considering writing a couple of programs in Python, but I
>> don't want to distribute the code along with them.
> This topic has been raised many times before, and there is a response
> which is now common but may sound harsh:
>
> What is it you think you would gain by obfuscating the code, and why is
> that worthwhile? What evidence do you have that code obfuscation would
> achieve that?
>
>> Finally, is there a good way to accomplish this? I know that I can
>> make .pyc files, but those can be disassembled very very easily with
>> the disassembler and shipping these still means that the person needs
>> the modules that are used. Is there another way to go about this?
> Not really, no. You would be best served by critically examining the
> requirement to obfuscate the code at all.
>


-- 

Take care,
Ty
my website:
http://tds-solutions.net
my blog:
http://tds-solutions.net/blog
skype: st8amnd127
“Programmers are in a race with the Universe to create bigger and better idiot-proof programs, while the Universe is trying to create bigger and better
idiots.  So far the Universe is winning.”
“If Java had true garbage collection, most programs would delete themselves upon execution.”