Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #64129

Re: Is it possible to protect python source code by compiling it to .pyc or .pyo?

Path csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path <ethan@stoneleaf.us>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.010
X-Spam-Evidence '*H*': 0.98; '*S*': 0.00; 'notice,': 0.07; 'subject:code': 0.07; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; 'reports.': 0.09; '~ethan~': 0.09; 'python': 0.11; 'bug': 0.12; 'jan': 0.12; '[1].': 0.16; 'subject: \n ': 0.16; 'subject:possible': 0.16; 'subject:python': 0.16; 'fix': 0.17; 'wrote:': 0.18; 'code.': 0.18; 'header:User- Agent:1': 0.23; 'adds': 0.24; 'subject: .': 0.24; 'source': 0.25; 'distribute': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; '[1]': 0.29; 'am,': 0.29; 'code': 0.31; 'yes.': 0.31; 'file': 0.32; 'bugs': 0.33; 'fri,': 0.33; 'done': 0.36; 'charset:us- ascii': 0.36; 'possible': 0.36; 'subject:?': 0.36; 'being': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'no.': 0.61; 'received:173': 0.61; 'offer': 0.62; 'myself': 0.63; 'sam': 0.68; 'protect': 0.79; 'compiling': 0.84; 'off,': 0.84; 'rip': 0.84; 'subject:source': 0.84; 'upstream': 0.84; 'received:gateway02.websitewelcome.com': 0.91
Date Thu, 16 Jan 2014 17:21:38 -0800
From Ethan Furman <ethan@stoneleaf.us>
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version 1.0
To python-list@python.org
Subject Re: Is it possible to protect python source code by compiling it to .pyc or .pyo?
References <7bf45fc1-e1c4-44f2-812c-e11ffa2c8ef3@googlegroups.com> <CAPTjJmp0T58xk1Ct6Pz43cH3y2fVwQJfy4Sk=QY0R1Vgps0uYQ@mail.gmail.com>
In-Reply-To <CAPTjJmp0T58xk1Ct6Pz43cH3y2fVwQJfy4Sk=QY0R1Vgps0uYQ@mail.gmail.com>
Content-Type text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding 7bit
X-AntiAbuse This header was added to track abuse, please include it with any abuse report
X-AntiAbuse Primary Hostname - gator3304.hostgator.com
X-AntiAbuse Original Domain - python.org
X-AntiAbuse Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse Sender Address Domain - stoneleaf.us
X-BWhitelist no
X-Source-IP 173.12.184.233
X-Source
X-Source-Args
X-Source-Dir
X-Source-Sender ([173.12.184.233]) [173.12.184.233]:60629
X-Source-Auth ethan+stoneleaf.us
X-Email-Count 1
X-Source-Cap dG9idWs7dG9idWs7Z2F0b3IzMzA0Lmhvc3RnYXRvci5jb20=
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.5617.1389921693.18130.python-list@python.org> (permalink)
Lines 18
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1389921693 news.xs4all.nl 2866 [2001:888:2000:d::a6]:56067
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:64129

Show key headers only | View raw


On 01/16/2014 05:09 PM, Chris Angelico wrote:
> On Fri, Jan 17, 2014 at 11:58 AM, Sam <lightaiyee@gmail.com> wrote:
>> I would like to protect my python source code. It need not be foolproof as long as it adds inconvenience to pirates.
>>
>> Is it possible to protect python source code by compiling it to .pyc or .pyo? Does .pyo offer better protection?

No and no.

> Distribute your code with a copyright notice, accept that a few people
> will rip you off, and have done with it.

Yes.  One of the nice things about Python is being able to fix bugs myself [1].

--
~Ethan~


[1] Yes, I file upstream bug reports.  :)

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Is it possible to protect python source code by compiling it to .pyc  or .pyo? Sam <lightaiyee@gmail.com> - 2014-01-16 16:58 -0800
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Ned Batchelder <ned@nedbatchelder.com> - 2014-01-16 20:07 -0500
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Ben Finney <ben+python@benfinney.id.au> - 2014-01-17 12:07 +1100
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Chris Angelico <rosuav@gmail.com> - 2014-01-17 12:09 +1100
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Ethan Furman <ethan@stoneleaf.us> - 2014-01-16 17:21 -0800
  Re: Is it possible to protect python source code by compiling it to .pyc  or .pyo? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-01-17 05:11 +0000
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Joshua Landau <joshua@landau.ws> - 2014-01-17 21:31 +0000
  Re: Is it possible to protect python source code by compiling it to .pyc or .pyo? Tim Delaney <timothy.c.delaney@gmail.com> - 2014-01-18 09:02 +1100

csiph-web