Re: python packaging infrastructure
> 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 greatly.
> I'd like to see Jython remain alive, at least until PyPy is mature
> enough to replace it. Have you looked at PyPy?
I have looked at it, and I think it is quite likely to (eventually)
replace Jython, though the timeframe for that may be long.
> Architecturally it
> sounds a lot like gcc except its "front-end" is for python only. 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. It
> should also require less manpower to keep the implementation
> working and up-to-date.
Yes, it has great promise, especially if it becomes the CPython backbone.
Regards,
-Frank
Reply to: