Re: 2.7.2 release schedule

--===============6563547509964787519==
Content-Type: multipart/alternative; boundary="000000000000dfbfef059c305a8e"

--000000000000dfbfef059c305a8e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for your responses, Jeffs. This was really helpful!

On Mon, Jan 13, 2020 at 9:56 AM Jeff Mitchell <[email protected]>
wrote:

>
> 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!
>
>
> _______________________________________________
> Jython-users mailing list
> [email protected]
>
> https://lists.sourceforge.net/lists/listinfo/jython-users
>

--000000000000dfbfef059c305a8e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for your responses, Jeffs. This was really helpful!=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Mon, Jan 13, 2020 at 9:56 AM Jeff Mitchell &lt;<a href=3D"mailto:jeff.mi=
[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><b=
r></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">On 06/01/2020 15:49, Jeff Mitchell wrote:<br>
&gt; I have found jython for 2.x to be exceedingly stable (thanks! <br>
&gt; wonderful piece of work over the years!) .. though you need to halfway=
 <br>
&gt; recent for ssl/encryption changes and stability fixes.<br>
<br>
I&#39;m glad you&#39;ve found it so. Although familiar mostly with its flaw=
s, <br>
now and then I stand far enough back to recognise how remarkable an <br>
achievement it is, and that I have the privilege of contributing to.<br></b=
lockquote><div><br></div><div>Any big flaws we should know about? or you me=
an just internal design flaws, which are inevitable for such a project? :)=
=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">&gt; Hijacking the thread though .. any news on jython3, or is there just=
 <br>
&gt; nto enough volunteer manpower? Every few months I google up and only <=
br>
&gt; find a repo from 2017, and various threads or questions but no <br>
&gt; answers. (And I wish I had time to jump in and help, same as everyone.=
.)<br>
&gt; --&gt; but is jython3 essentially dead for now?<br>
<br>
I don&#39;t think so. The main problem with that repo is that 2.7 moved on =
a <br>
lot since the fork, and since basic things like str changed from 2 to 3, <b=
r>
there are technical problems merging. We also say amongst ourselves <br>
&quot;we&#39;ll do that differently in 3&quot; and it is difficult to see h=
ow you <br>
could, starting from there. 3 looks like a great opportunity for change, <b=
r>
but the more one takes on, the longer it will be. Fortunately I have <br>
some time, but it has to be divided with 2.7.<br></blockquote><div><br></di=
v><div>Appreciate the insider view :) From the outside though .. I&#39;d as=
sume at least a couple years before jython3 is usable.</div><div><br></div>=
<div>Maybe update some &#39;signs of life&#39; somewhere on the website or =
repo might be wise, as I&#39;ve seen a few people asking around this over t=
he months? *shrug*</div><div><br></div><div>Thank you (and the team!) again=
!</div><div><br></div><div><br></div></div></div>
_______________________________________________<br>
Jython-users mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Jyt=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/jython-users" rel=
=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listi=
nfo/jython-users</a><br>
</blockquote></div>

--000000000000dfbfef059c305a8e--



--===============6563547509964787519==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============6563547509964787519==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============6563547509964787519==--