Dropping py3.8, working on py3.10

We have begun work on py3.10. I changed the buildbot configuration to 
build default (py2.7), py3.9, py3.10 instead of default (py2.7), py3.8, 
py3.9. Builds for py3.8 (or any branch) can be kicked off manually. 
Unless there is significant push-back, or some latent urgent bug appears 
on py3.8, I do not plan on making another py3.8 release.


Help is always welcome, the py3.10 work is at a stage of "death by 1000 
paper cuts" where there are many small details that need to be changed. 
One thing people could do is to peruse the lib-python failures (testing 
py3.10 on the upstream stdlib tests) for obvious [2] problems. You can 
see the log file by looking at the latest builds [0] -> clicking on the 
pypy-c-jit-linux-x86-64 link -> shell_16 lib-python test failed -> 
stdio. There are some hints for parsing that output on the wiki [1].


Matti


[0] https://buildbot.pypy.org/summary?branch=py3.10

[1] https://foss.heptapod.net/pypy/pypy/-/wikis/Analysing-lib-python-errors

[2] what may be obvious to you may be gibberish to someone else, which 
is why we need everyone's expertise

_______________________________________________
pypy-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/pypy-dev.python.org/
Member address: [email protected]