From: Jeff M. <jef...@za...> - 2020-01-13 14:55:47
|
> On 06/01/2020 15:49, Jeff Mitchell wrote: > > I have found jython for 2.x to be exceedingly stable (thanks! > > wonderful piece of work over the years!) .. though you need to halfway > > recent for ssl/encryption changes and stability fixes. > > I'm glad you've found it so. Although familiar mostly with its flaws, > now and then I stand far enough back to recognise how remarkable an > achievement it is, and that I have the privilege of contributing to. > Any big flaws we should know about? or you mean just internal design flaws, which are inevitable for such a project? :) > Hijacking the thread though .. any news on jython3, or is there just > > nto enough volunteer manpower? Every few months I google up and only > > find a repo from 2017, and various threads or questions but no > > answers. (And I wish I had time to jump in and help, same as everyone..) > > --> but is jython3 essentially dead for now? > > I don't think so. The main problem with that repo is that 2.7 moved on a > lot since the fork, and since basic things like str changed from 2 to 3, > there are technical problems merging. We also say amongst ourselves > "we'll do that differently in 3" and it is difficult to see how you > could, starting from there. 3 looks like a great opportunity for change, > but the more one takes on, the longer it will be. Fortunately I have > some time, but it has to be divided with 2.7. > Appreciate the insider view :) From the outside though .. I'd assume at least a couple years before jython3 is usable. Maybe update some 'signs of life' somewhere on the website or repo might be wise, as I've seen a few people asking around this over the months? *shrug* Thank you (and the team!) again! |