On Fri, 2006-01-13 at 00:33 -0600, Joe Wreschnig wrote:
> Unless I misunderstand (either or or python-support) it does,
Should be ^- "either you or python-support"
--
Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
On Thu, 2006-01-12 at 14:44 +0100, Matthias Klose wrote:
> After a long silence (and some work on "unrelated" C++ transitions ;),
> an update to the python packaging infrastructure.
Thank you. I've snipped stuff I agree with, or don't have an opinion on
yet.
>- modules are installed into a di
Hi,
I should probably check in to this discussion, since I'm the current
(inactive) maintainer of jython -- I put it up for adoption several
months ago since I don't have so much time these days and I no longer
have much involvement with either java or jython.
A couple of notes:
- I'll probably
> 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
> > 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
> 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
On Thu, Jan 12, 2006 at 11:54:18AM -0500, Derrick Hudson wrote:
> | Anyhow, I hate to see Jython orphaned, perhaps down the road (after
> | the next Jython release) I'll come back to find out what it takes to
> | take over the package maintenance of Jython in Debian.
>
> I'd like to see Jython
On Thu, Jan 12, 2006 at 05:09:56PM +0100, Wouter van Heyst wrote:
[jython]
| Is there any reason it can't work with 2.4?
Yes. The most recent release (2.2a1) doesn't implement the new
language constructs introduced by CPython 2.3 and 2.4.
-D
--
If we claim we have not sinned, we make Him out
On Thu, Jan 12, 2006 at 10:52:43AM -0500, Frank Wierzbicki wrote:
| > 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 glad to see someone is working on it.
On Thu, Jan 12, 2006 at 10:52:43AM -0500, Frank Wierzbicki wrote:
> > 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 r
> 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
After a long silence (and some work on "unrelated" C++ transitions ;),
an update to the python packaging infrastructure.
We want to change the default python version used to the recent
python-2.4.2 release, and change it again to 2.5.0, when/if this
version is released before etch freezes. Furthe
12 matches
Mail list logo
