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


Groups > comp.lang.python > #78588

Re: Obscuring Python source from end users

References <89381545-5edc-4f85-a4b8-86eebfdf34ee@googlegroups.com> <CAPTjJmpgu-rmHLBwdeNASx9Cim5rWz-VPN+FbMGQ9tiT_9PDxQ@mail.gmail.com> <mailman.14473.1412002507.18130.python-list@python.org> <m0j04o$61o$1@news.albasani.net>
Date 2014-10-02 18:32 +1000
Subject Re: Obscuring Python source from end users
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.14543.1412238739.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Thu, Oct 2, 2014 at 5:50 PM, Johannes Bauer <dfnsonfsduifb@gmx.de> wrote:
> On 29.09.2014 16:53, Sturla Molden wrote:
>> Chris Angelico <rosuav@gmail.com> wrote:
>>
>>>> I have a project that involves distributing Python code to users in an
>>>> organisation. Users do not interact directly with the Python code; they
>>>> only know this project as an Excel add-in.
>>>>
>>>> Now, internal audit takes exception in some cases if users are able to
>>>> see the source code.
>>>
>>> The solution is to fix your internal audit.
>>
>> +1
>
> You two have obviously never worked at a large corporation or you would
> both realize how tremendously naive and unhelpful this "solution" is.

Unhelpful? Perhaps, perhaps not. I would, however, distinguish between
the two parts of my original response as follows:

1) The *solution* is to fix the audit process.

2) But here's one of several *work-arounds*.

It may well be impossible to truly solve the problem, and I'm aware of
that. But sometimes you need to point out that a pyc-only distribution
is still distributing something very VERY close to the source code,
and therefore it's nigh useless to talk of not distributing Python
source.

ChrisA

Back to comp.lang.python | Previous | Next — Previous 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