Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Marko Rauhamaa Newsgroups: comp.lang.python Subject: Re: Obscuring Python source from end users Date: Thu, 02 Oct 2014 08:17:40 +0300 Organization: A noiseless patient Spider Lines: 13 Message-ID: <8738b7t5hn.fsf@elektro.pacujo.net> References: <89381545-5edc-4f85-a4b8-86eebfdf34ee@googlegroups.com> <542946ec$0$12998$c3e8da3$5496439d@news.astraweb.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx05.eternal-september.org; posting-host="ff5cf27ef3d5b31f034d3b72bdc27a41"; logging-data="31371"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/phCTSMET9QXg7k2u+Qez7" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:JpAEN3T7/eIKQcLdYcHUyAqm8WU= sha1:fOLJ4xwzPpxmTdP9BUH5VbkEqJw= Xref: csiph.com comp.lang.python:78578 Dan Stromberg : > On Mon, Sep 29, 2014 at 4:47 AM, Steven D'Aprano >> Yes. Distribute the pyc files only. > > Yes, this is the way it's usually done. Has the .pyc file format stabilized? A decade ago, my employer shipped an application as .pyc files but had to ship the matching CPython binary with it. Marko