Compiling Python

[Kragen Sitaker]

"Steve Holden" <sholden at holdenweb.com> writes:
> "Jeff Epler" <jepler at unpythonic.net> wrote ...
> > On Thu, Jun 06, 2002 at 12:58:59PM -0400, Kragen Sitaker wrote:
> > > "Edward K. Ream" <edream at tds.net> writes:
> > > > BTW, a compiled version of a Python program would be valuable
> > > > commercially, as it would allow companies to protect their source
> code,
> > > > as well as (possibly) improve performance.
> > >
> > > I'm worried about this myself; perhaps the compiler could include the
> > > source code in the resulting executable to prevent this.
> >
> > Your sarcasm is lost on me.
> 
> Lost, perhaps, but (since you recognised it) not entirely wasted ;-)

I don't know why you thought I was being sarcastic.  I was completely
serious.

The Java guys have probably a better solution: don't save the compiled
code to disk.  A traditional compiler that included the source code in
the executable (like, approximately, javac) could easily be hacked to
remove the source code; but turning a JIT compiler into a traditional
compiler is a bit more work.