Menu
▾
▴
[Jython-dev] Jython 3 merging effort / Was: Re: Jython sprint, 25th and 26th of November, Düsseldorf, Germany
|
From: Stefan R. <Ste...@gm...> - 2017-11-23 19:01:34
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div>> Merging means pulling from 2.7 to 3, I think.</div> <div> </div> <div>I'm actually going to try it the other way round.</div> <div> </div> <div>The current situation with Jython 3 concerns me a bit. It seems to</div> <div>be in a state where it is unclear how to proceed. This makes it</div> <div>somewhat discouraging to work on it. So I think we need a proper</div> <div>plan how to go on. I'd suggest the following:</div> <div> </div> <div>We open a new fresh Jython 3 that starts at Jython 2.7.2 release.</div> <div>Keep in mind that the Jython 3 repository is actually a *sandbox*</div> <div>so far. We merge every commit done to Jython 3 sandbox since it</div> <div>was forked from 2.7, (hopefully mainly via automatic merge</div> <div>mechanism). This is the ideal opportunity to triage the issue</div> <div>with broken Windows support and to review Isaiahs work. While</div> <div>he did a lot great work on Jython 3 we must keep in mind that it</div> <div>has been hardly reviewed so far.</div> <div>I hope we can end up with a workable Jython 3 containing all the</div> <div>bugfixes and improvements that were added in Jython 2.7.1 and 2.</div> <div>Problematic commits can be sorted out for later additional review.</div> <div> </div> <div>Regarding some aspects I propose to directly target Python 3.7, e.g.</div> <div>bytecode level and language syntax. Going through intermediate</div> <div>versions would be multiple work here.</div> <div> </div> <div>Besides this merging work we will need a real roadmap that states</div> <div>all the milestones and steps required for a Jython 3 release. Who</div> <div>of us knows Python well enough to put this together? Jim? Frank?</div> <div> </div> <div>After merging is done we need a clear policy about backporting etc.</div> <div>I'd suggest to focus on Jython 3 then and only backport crucial or</div> <div>cherry-picked bugfixed to 2.7 branch.</div> <div> </div> <div>In the sprint I'll start an inofficial experimental Jython 3 to work on merging.</div> <div>This can maybe form the basis for an official non-sandbox Jython 3.</div> <div> </div> <div>Thoughts?</div> <div> </div> <div> </div> <div>-Stefan</div> <div> </div> <div> </div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Donnerstag, 23. November 2017 um 19:03 Uhr<br/> <b>Von:</b> "Jeff Allen" <ja...@fa...><br/> <b>An:</b> "Stefan Richthofer" <Ste...@gm...><br/> <b>Betreff:</b> Re: [Jython-dev] Jython sprint, 25th and 26th of November, Düsseldorf, Germany</div> <div name="quoted-content"> <div style="background-color: rgb(255,255,255);"> <p>Good initiative, but too far for me. :) I will be working on Jython in some way this weekend, of course.</p> <p>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.</p> <p>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.</p> Jeff<br/> <pre class="moz-signature">Jeff Allen </pre> <div class="moz-cite-prefix">On 22/11/2017 15:34, Stefan Richthofer wrote:</div> <blockquote> <pre>Dear Jython developers and users, Next weekend is another Python sprint by "Python Meeting Düsseldorf", <a class="moz-txt-link-freetext" href="https://www.meetup.com/Python-Meeting-Dusseldorf/events/243737124/" target="_blank">https://www.meetup.com/Python-Meeting-Dusseldorf/events/243737124/</a>. (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 <a class="moz-txt-link-freetext" href="http://bugs.jython.org/issue2487" target="_blank">http://bugs.jython.org/issue2487</a> and <a class="moz-txt-link-freetext" href="http://bugs.jython.org/issue2570" target="_blank">http://bugs.jython.org/issue2570</a>) - 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! <a class="moz-txt-link-freetext" href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a> _______________________________________________ Jython-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a> </pre> </blockquote> </div> </div> </div> </div> </div></div></body></html> |
