On Fri, Sep 25, 2026 at 8:58 AM Ronny Pfannschmidt <[email protected]> wrote: > > Hi everyone, i finished the first milestone i set for myself - which was > rypthon is python3 syntax and it runs/works. now its time to reshuffle and > land those bits so its can be build on. its visible under > https://github.com/RonnyPfannschmidt/pypy/pull/1 - but expect churn to come > up as i prepare eventual actual prs/a pr stack. a key fun bit was creating a > new assert rewrite hook that is rflow compatible plus plays into my future > plans on having annotated/debuggable assertion as part of python itself as > next steps i want to resuffle the pr a bit to be on more merge friendly > comits that should each carry over a enhancement Im also preparing updates to > the ci docker images, but cot.assert may have more churn than desirable for a > while > > i'd appreciate feedback on the order of things and reach some consensus on > how to merge things going forward > > -- Ronny
Thanks for working on this, > Questions > > Is "valid Python 3 syntax across rpython/" a milestone you are happy to have > on main, given that it changes nothing about running on Python 3 yet? Sure, especially since (I think) you added a test we do not break this. It might enable building the docs with python3. > Does "small PRs on main, propagate through the regular merges" work for you? > Or would you rather land in larger batches, or on the py3.x branches directly? Let's stick with PRs to main. Note that the CI runs all rpython tests on all platforms. > For the main → py3.x merges: are mechanical sweeps across rpython/ a burden, > or fine given how close rpython/ is on both sides? Is there a time you would > prefer they land, for example right after a merge? I think it doesn't really matter. Since this is only rpython at the moment, it should not affect py3 at all. > Pytest: one shared pytest for main and py3.x, or a per-branch vendored copy > for now? Would the pytest3.10 branch > (https://github.com/pypy/pypy/commits/pytest3.10/) be the preferred base? I never finished the pytest3.10 branch. I started a PR to see how far that branch got https://github.com/pypy/pypy/pull/5595. > What PR size is comfortable to review? Definitely break this into reviewable chunks, around a topic would probably be the easiest, but it is hard to know > Should anything outside rpython/ be in scope yet? I have kept away from > pypy/, since it diverges between branches. Let's leave pypy out for now, this is enough to digest as it is. > Each commit carries a Co-Authored-By trailer naming the model and harness. Matti _______________________________________________ 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]
