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


Groups > comp.lang.python > #78451

Re: Obscuring Python source from end users

X-Received by 10.182.4.8 with SMTP id g8mr7569414obg.24.1411980095793; Mon, 29 Sep 2014 01:41:35 -0700 (PDT)
X-Received by 10.140.96.54 with SMTP id j51mr5261qge.13.1411980095724; Mon, 29 Sep 2014 01:41:35 -0700 (PDT)
Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!uq10no132561igb.0!news-out.google.com!i10ni45qaf.0!nntp.google.com!dc16no80780qab.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups comp.lang.python
Date Mon, 29 Sep 2014 01:41:35 -0700 (PDT)
In-Reply-To <mailman.14461.1411977165.18130.python-list@python.org>
Complaints-To groups-abuse@google.com
Injection-Info glegroupsg2000goo.googlegroups.com; posting-host=196.8.123.40; posting-account=rnL3ZAoAAADtwW2xIoMdlSvnvnZDXEzi
NNTP-Posting-Host 196.8.123.40
References <89381545-5edc-4f85-a4b8-86eebfdf34ee@googlegroups.com> <mailman.14461.1411977165.18130.python-list@python.org>
User-Agent G2/1.0
MIME-Version 1.0
Message-ID <9ad69bd8-ca77-438f-adfe-87d727ca170c@googlegroups.com> (permalink)
Subject Re: Obscuring Python source from end users
From norman.ives@gmail.com
Injection-Date Mon, 29 Sep 2014 08:41:35 +0000
Content-Type text/plain; charset=ISO-8859-1
Xref csiph.com comp.lang.python:78451

Show key headers only | View raw


Thanks for the reply!

I'm not concerned about hiding the source code in a fundamental way. The condition that needs to be satisfied is that independent validators (in the organisation) must not "have access" to the source code.

Crunching the source is an interesting idea that could achieve that end, but it seems fraught with problems like maintaining consistency between renaming objects in a module and renaming where imports happen.

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


Thread

Obscuring Python source from end users norman.ives@gmail.com - 2014-09-29 00:36 -0700
  Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 17:52 +1000
    Re: Obscuring Python source from end users norman.ives@gmail.com - 2014-09-29 01:41 -0700
      Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 18:55 +1000
      Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 20:14 +1000
  Re: Obscuring Python source from end users alister <alister.nospam.ware@ntlworld.com> - 2014-09-29 08:42 +0000
  Re: Obscuring Python source from end users Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-09-29 21:47 +1000
    Re: Obscuring Python source from end users Sturla Molden <sturla.molden@gmail.com> - 2014-09-29 14:51 +0000
    Re: Obscuring Python source from end users Dan Stromberg <drsalists@gmail.com> - 2014-10-01 15:06 -0700
      Re: Obscuring Python source from end users Marko Rauhamaa <marko@pacujo.net> - 2014-10-02 08:17 +0300
        Re: Obscuring Python source from end users Terry Reedy <tjreedy@udel.edu> - 2014-10-02 03:19 -0400
        Re: Obscuring Python source from end users Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-10-02 17:22 +1000
  Re: Obscuring Python source from end users Sturla Molden <sturla.molden@gmail.com> - 2014-09-29 14:53 +0000
    Re: Obscuring Python source from end users Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-10-02 09:50 +0200
      Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-10-02 18:32 +1000

csiph-web