> > If the portability problem can be solved by checking things into Jython
> > instead, I think I would prefer that.
I'm definitely interested in bringing ElementTree into Jython at some
point, though I probably won't have time to look into it until after
the next Jython release. I'm quite sure
On 12/13/05, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Fredrik Lundh wrote:> BTW, what's the policy wrt. Jython-specific modules in the standard library?I don't think there is enough precedence to have a policy. So far, theonly places that explicitly support Jython is the test suite, pickle,
and
Fredrik Lundh wrote:
> BTW, what's the policy wrt. Jython-specific modules in the standard library?
I don't think there is enough precedence to have a policy. So far, the
only places that explicitly support Jython is the test suite, pickle,
and platform (I wouldn't really count in site here).
If
I'm no expert on policy any more, but if you can reasonably prevent it
from doing any harm (such as failing unit tests) to CPython I don't
see why not. However I believe that traditionally, Jython-specific
code has been checked into Jython's own source control.
--Guido
On 12/13/05, Fredrik Lundh
BTW, what's the policy wrt. Jython-specific modules in the standard library?
Expat isn't available under Jython, but I have a Java/Jython-driver for
ElementTree
on my disk. Can / should this go into the CPython standard library ?
___
Python-Dev m
