[Info-vax] Python and various libraries updated

[Jan-Erik Söderholm]

Den 2020-08-03 kl. 14:57, skrev Jean-François Piéronne:
>>
>> Hi. And many thanks for your efforts!
>>
>> I can now see two new LD images but I do not understand the naming.
>> There are two "jfppy0700a_278.zip", one with, and one w/o, ";1".
>> And then one new "jfppy1400a.zip".
>>
>> You wrote that "most of the libraries and Python 2.7 for AXP has
>> been updated". Should one of these been named "jfplibxxxxx.zip"?
>>
>> Index of /anonymous/kits/axp/images_ld/
> [snip]
> Thanks, this is fixed.

Ah, right. That was differnt. I notice that the "lib" part is now
more then 3 times larger than the previous kit while the basic
Python LD disk actually is slightly smaller...

Index of /anonymous/kits/axp/images_ld/
jfplib0008A.zip       31-Oct-2014 08:19            41162971
jfplib0020a.zip       03-Aug-2020 09:58           137831060
jfppy0700a_278.zip    31-Oct-2014 08:24            72044024
jfppy1400a_2718.zip   03-Aug-2020 09:58            68755032

Time to download to our test system. I do not really remember if
I have patched anything directly into our current LD disks...

> 
>>
>> You also mention Python 3.10a0.
>>
>> But "https://docs.python.org/dev/" says:
>>
>> Docs by version:
>> Python 3.10 (in development)
>> Python 3.9 (pre-release)
>> Python 3.8 (stable)
>>
>> Any specific reason to port a "in development" version?
>> Or have I missed that 3.8 is already ported (?).
> 
> Python 3.10 is will be release next year, so my goal is to have the
> latest Python version available when VMS on X86 will be production ready.
> 

OK. probably the right goal... :-)

> Another goal is to have a version which will be maintained for many years.
> 
> Not porting 3.8 or, now 3.9, is just because I do not have enough time.
> But it is doable, need to back port the patches to the corresponding
> branches. Having patches include in the default branch will make release
> of future version simple.
> 
> I have included some of the patches included in the old 3.5 port, but
> not all sources are provided, or are not usable on recent Python 3 version.
> 
> With one customer, we have started to port a fairly large application
> without, currently, many problems. The 2to3 tools work much better than
> I have initially expected. Also having the same extensions than in
> Python2 is a big help.

So that port is using the current IA64 3.10 port? I guess you expect
3.10 to be reasonable stable from now and up to the formal release?

Is VSI involved in any way at all in these Python related work?

> 
> 
> 
> JF
>