Python 2.0

[Stidolph, David]

Speaking for myself, we are using Python as an embedded language for an
application to add scripting abilities to it.  We decided to go with Python
instead of Java because of the C-Level interface.  It gave us the confidence
that we could "hack" into Python when it was required.  That would not be
practical for a Java version of Python.

The main thing I would like about JPython would be the Just In Time
compilers available for it.

-----Original Message-----
From: graham at sloth.math.uga.edu [mailto:graham at sloth.math.uga.edu]
Sent: Friday, May 28, 1999 4:14 PM
To: python-list at cwi.nl
Subject: Re: Python 2.0


Michael P. Reilly (arcege at shore.net) wrote:
: But I do have to ask, what do you find lacking with JPython, Graham?
: It is Python written in Java, on the JVM, with full API support (as far
: as I have determined), and supposed "true garbage collection".  JPython
: functions/methods are written in Java bytecode, not in Python bytecode
: (according to the docs).

I have used JPython (that's where the orginal quote that started this
message came from). My point is that I think implementation via Java is
a good idea and I am wondering if that is being considered for the
future of CPython. ie. abandoning the CPython implementation as the
main Python and adopting a Java implementation instead (reversing the
status of CPython and JPython).

graham
-- 
                      Je suis pour le communisme
                      Je suis pour le socialisme
                      Je suis pour le capitalisme
                     Parce que je suis opportuniste