[Python-Dev] Re: descr PLAN.txt

[Samuele Pedroni]

> > I think and it seems it contains some useful information
> > for when we try to port the descr changes to jython,
> > or will all this stuff be  completely documented somewhere else?
> 
> Hopefully the PEPs will be much more complete records.  PLAN.txt was
> just my own to-do list, indicating how far I was along the realization
> of the PEPs.  I realize that the PEPs are currently behind, but it is
> in the PLAN.txt to remedy this. :-)

I see.

> I'm glad you are planning to copy this effort in Jython.  

Yes I'm planning to do try that.
I don't think that without keeping up with Python Jython
can survive. Not that we are very fast at keeping up OTOH.

(yes for very practical reasons I'm among
those who would prefer a slower development for Python :))

> (It should
> actually be simpler in Jython as it doesn't have so much of a
> dichotomy between types and classes as C-Python does.)

I take this as an  encouragement but actually the good point
is that Java is bit more productive than multi-platform C, that's
all.

You should consider that we have to integrate the changes
with the whole Java interoperability architecture and
that we should deal with the limitations of java reflection
and probably invent some new kind of inheriting from java,
different from what is already there,
that means new code that should produce dynamically
some java bytecode ...

>  If there's
> anything I can do to help (short of coding in Java :-) please let me
> know.  In particular, if there's anything unclear in the PEPs or
> PLAN.txt or in python.org/2.2/descrintro.html or anywhere else
> (including the C code), I'd be happy to clarify it at your (or anybody
> else's) request.  

Thanks, I imagine we will have some questions :)

> (Is Finn Bock still around in Jython?)

AFAIK yes. For 2.1 (yet not out) he has done:
- rich comparison
- new coercion model
- weak ref support
- importing from jars on sys.path
...

I have done:
static nested scopes
fixed some old nasty bugs
improved the compatibility of importing wrt CPython

And in any case I hope so:

given that for 2.2 we have to do:
iterators
generators
descr

both in the runtime and jythonc ...

and our user base so far has been quite passive.

Sorry for the rants.

regards.