Re: python packaging infrastructure

2006-01-12 Thread Frank Wierzbicki
> It should be practical to create Java templates for PyPy to use in the > backend to produce a python implementation that executes in a JVM. There is one snag to "Java" templates -- since Java has no goto, good implementations of generators are difficult. The templates might have to be bytecode

Re: python packaging infrastructure

2006-01-12 Thread Frank Wierzbicki
> > It should be practical to create Java templates for PyPy to use in the > > backend to produce a python implementation that executes in a JVM. > > I can't back it up, but I thought this was possible already, as well as > a clisp backend. I know for certain C and LLVM work. I'm quite sure there i

Re: python packaging infrastructure

2006-01-12 Thread Frank Wierzbicki
> I think it was a good idea at the time to avoid duplicating all of the > pure-python modules in the standard library. However, given that > Jython's development hasn't kept pace with CPython I think that > eliminating the dependency would be a better choice now. That would simplify the issue gre

Re: python packaging infrastructure

2006-01-12 Thread Frank Wierzbicki
> At least jython isn't an issue anymore (orphaned, and > new upstream snapshots available) Hi Matthias, I am (recently) the primary maintainer of the (upstream) Jython project. I'm also a big fan of Debian. The next release of Jython will depend on either Python 2.2 or Python 2.3, if it gets pa