X-Received: by 10.58.100.99 with SMTP id ex3mr4645759veb.1.1389920329017; Thu, 16 Jan 2014 16:58:49 -0800 (PST)
X-Received: by 10.50.13.7 with SMTP id d7mr2550igc.16.1389920328840; Thu, 16 Jan 2014 16:58:48 -0800 (PST)
Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!6no14059823qao.1!news-out.google.com!gg4ni5548qab.0!nntp.google.com!p15no18420194qaj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.python
Date: Thu, 16 Jan 2014 16:58:48 -0800 (PST)
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=202.12.95.96; posting-account=04sJLgoAAAAgAAqZKXYX9p_DIU_5YHlA
NNTP-Posting-Host: 202.12.95.96
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7bf45fc1-e1c4-44f2-812c-e11ffa2c8ef3@googlegroups.com>
Subject: Is it possible to protect python source code by compiling it to .pyc or .pyo?
From: Sam <lightaiyee@gmail.com>
Injection-Date: Fri, 17 Jan 2014 00:58:48 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: csiph.com comp.lang.python:64120

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?