Re: [Jython-dev] Dev status

[Carlos Q. <car...@we...>]

On Friday 28 September 2001 19:01, Samuele Pedroni wrote:
Hi Samuele, thanks for answering, I'll try to colborate ond post some patches 
for the bugs you mentioned.

What about new modules, which ones are going to be added, or if you want how 
to make a CPython package qualify as acceptable to Jython?

Regards

> Hi.
>
> > Hi
> >
> > I've noticed that the development hasn't been advancing lately, at least
> > I haven't get anything with a CVS update. I'd like to ship a stable 2.1
> > version soon.
> >
> > If there is something I could do to help, some tasks or bugs to fix, I'd
> > be willing to invest some time on that,
>
> No idea of where Finn is hiding :), lately he has not posted anything.
>
> So I speak for myself. Yes the development is a bit sluggish.
> What it remains to do for 2.1:
>
> Here is what should be done or at least tried before we ship, Finn
> position could be different.
>
> About the bugs:
>
> These are good old friends some even historical, I would say out of
> priority. __builtin__.id() does not return unique values for different
> multi-line statements in the JPython interpreter
> Can't acces public member of package private base class
> __getitem__ expected, but not defined for java exc.
>
> Out of the rest I think the following are important:
>
> * open('test.txt','w').write('test')
> which in this form cannot be solved but is related to the problem
> of properly flushing files not closed by the user, there have
> been some discussion on the list, and Finn had some ideas.
>
> * Tuple unpacking raises KeyError
> this is taken by Finn: no idea
>
> * jythonc 2.1a3 --package problem
> * jythonc --deep pjy$packages problem
> These are my fault, I know how to solve so ...
> I will probably take care also of
> *case insensitivity on import causes prob
> too
>
> *PackageManager doesn't work correctly
> *pickle.load gives wrong result
> Both need to be analyzed
>
> * Missing 'lastindex' on match objects
> This should be easy but not already checked.
>
> * builtin method as a class variable
> This is somehow important (is needed by phabric)
> and is probably quite tricky.
>
> The rest is low prio.
>
> Finally:
> *Tracking variables across packages
> should become a low priority feature request, probably is too much
> work to be ever implemented, at least not by me.
>
> For the tasks:
> we need to implement or fake xreadlines and the corresponding
> method for files.
>
> And finally the fate of the patches should be decided, but none
> of them is high prio, the one by Otmar Humbel is nice but needs
> some tweaking (hoping the feature will be more helpful than confusing)
>
> If you want to pick something just say it here, and post a patch
> to SF. This holds for everyone. And obviously thanks.
>
> regards.
>
>
>
>
>
>
>
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev