Jython 3 merging effort / Was: Re: Jy thon sprint, 25th and 26th of November, Düsseldorf, Germany

> Merging means pulling from 2.7 to 3, I think.

I'm actually going to try it the other way round.

The current situation with Jython 3 concerns me a bit. It seems to

be in a state where it is unclear how to proceed. This makes it

somewhat discouraging to work on it. So I think we need a proper

plan how to go on. I'd suggest the following:

We open a new fresh Jython 3 that starts at Jython 2.7.2 release.

Keep in mind that the Jython 3 repository is actually a *sandbox*

so far. We merge every commit done to Jython 3 sandbox since it

was forked from 2.7, (hopefully mainly via automatic merge

mechanism). This is the ideal opportunity to triage the issue

with broken Windows support and to review Isaiahs work. While

he did a lot great work on Jython 3 we must keep in mind that it

has been hardly reviewed so far.

I hope we can end up with a workable Jython 3 containing all the

bugfixes and improvements that were added in Jython 2.7.1 and 2.

Problematic commits can be sorted out for later additional review.

Regarding some aspects I propose to directly target Python 3.7, e.g.

bytecode level and language syntax. Going through intermediate

versions would be multiple work here.

Besides this merging work we will need a real roadmap that states

all the milestones and steps required for a Jython 3 release. Who

of us knows Python well enough to put this together? Jim? Frank?

After merging is done we need a clear policy about backporting etc.

I'd suggest to focus on Jython 3 then and only backport crucial or

cherry-picked bugfixed to 2.7 branch.

In the sprint I'll start an inofficial experimental Jython 3 to work on merging.

This can maybe form the basis for an official non-sandbox Jython 3.

Thoughts?

-Stefan

Gesendet: Donnerstag, 23. November 2017 um 19:03 Uhr

Von: "Jeff Allen" <[email protected]>

An: "Stefan Richthofer" <[email protected]>

Betreff: Re: [Jython-dev] Jython sprint, 25th and 26th of November, Düsseldorf, Germany

Good initiative, but too far for me. :) I will be working on Jython in some way this weekend, of course.

Merging means pulling from 2.7 to 3, I think. Putting them in the same repository, as two branches, ought not to be a problem, but doesn't achieve much.

Working productively with 3 has defeated me so far, as Isaiah's changes broke it for Windows and I've not figured out recreate the lumps of binary where it broke. (Also I think that approach is a tactical error for us.) I think maybe a sort of zip-fastener approach is needed working from the point of divergence, simulating a process that might have happened along the way.

Jeff

Jeff Allen

On 22/11/2017 15:34, Stefan Richthofer wrote:

Dear Jython developers and users,

Next weekend is another Python sprint by "Python Meeting Düsseldorf", https://www.meetup.com/Python-Meeting-Dusseldorf/events/243737124/ . (25th and 26th of November in Düsseldorf, Germany)
I'll be offering a sprint on Jython there. More specifically I hope we can look into merging Jython 2.7 trunk and Jython 3 sandbox.
I'm aware that hardly anyone from this list can make it there in person (if so, even better!), but please feel encouraged to participate remotely via Jython's IRC-channel irc://irc.freenode.net/#jython. We will be online there 11.00-17.30 CET each day (and hopefully fill it with more activity than usual).

Potential topics include:

Using Jython:
- Jython basics / getting started
- Python/Java integration (e.g. calling Java from Python and vice versa)
- scripting Java with Jython
- GUI with JavaFX in Python

Developing Jython:
- Jython internals / getting started
- Bugfixes in Jython core - Can we fix some actual bugs?
(I will especially look into current release blockers http://bugs.jython.org/issue2487 and http://bugs.jython.org/issue2570 )
- Merging Jython 2.7 trunk and Jython 3 sandbox

Experimental stuff (What is already workable? Let's try!):
- JyNI (e.g. NumPy, ctypes)
- Jython 3

Individual stuff:
- You have some project or usecase for Jython and need advice?
- There is some specific gap keeping you from using Jython? -- Maybe we can fix it or work around.
-- Maybe even if it involves a C-Extension (let's tweak JyNI)

Looking forward to work with you!

-Stefan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev