Mailman 3 September 2023 - pypy-dev

PyPy bugfix release 7.3.13
by Matti Picus 27 Sep '23

27 Sep '23

I am going to create a new release 7.3.13 to fix a problems in the conda feedstock. I improved the support for multiphase c-extension initialization immediately after the 7.3.12 release, and tried to merge pieces of it to the conda-forge feedstock but it has become too many patches to maintain. If there is anything you think I should add to the release, please file an issue and mark it with the 7.3.13 milestone. If the CFFI 1.16 release happens before I get too deep into the PyPy release process, I will try to update it. I had hoped to get most of hpy0.9 into this release, but there is still a lot to do. Matti

1 0

Improve symlink support for DirEntry on Windows
by cpburnz＠gmail.com 22 Sep '23

22 Sep '23

Hi PyPy devs, In one of my projects I noticed tests involving symlinked directories on Windows failing on PyPy 3.9/10 (v7.3.12), but succeeding on CPython 3.9/10. After digging into `pypy/module/posix/interp_scandir.py`, it looks like `W_DirEntry` has an incomplete implementation for Windows. The `W_DirEntry.is_*()` methods only return results for the symlink (the *follow_symlinks* argument is ignored via `.check_mode()`). The `W_DirEntry.stat()` method only returns the `stat_result` for the target file (ignoring the *follow_symlinks* via `.get_stat_or_lstat()`). I have a proof of concept fixing the Windows implementation based upon the adjacent POSIX code. It passes the previously skipped tests `test_stat4`, and `test_dir3-6` in `pypy/module/posix/test/test_scandir.py`. My modification to `test_scandir.py` is kind of janky to support Python 2.7 on Windows because it doesn't natively support `os.symlink()`. The test uses `pypy.module.posix.interp_posix.symlink` when `os.symlink` is unavailable. I'm not sure how to run `test_scandir.py` after compiling/translationing, and what other tests I should be running. I can successfully compile these modifications on the py3.10 branch on Windows 10 and Linux (Manjaro, an Arch Linux derivative). The Contributing Guidelines recommends that I start with the mailing list before making a random merge request. What's the next step in possibly getting this fix reviewed? Regards, Caleb Burns

3 4

tezos proof generating vm with pypy?
by simon.parry＠karoshibee.com 13 Sep '23

13 Sep '23

Hello, I'm starting to spec out how much work/what to do to make a first cut of a proof generating virtual machine (PVM <https://tezos.gitlab.io/alpha/smart_rollups.html> ) for python with pypy (specifically sandboxed2 pypy - but maybe I worry about that later). My understanding is, this is very general and high level, that I would need to modify the running of the pypy interpreter to output certain cryptographic objects at each low-level step of the pypy vm. So as a first jump into the code I was wondering if there is already some sort of interpreter-tracing system (e.g. for debugging or profiling) already in place that I could monkey about with? Ps I've already checked the pypy code out from hg and built my own pypy3.10-c etc, that's all fine. Thanks Simon

1 0

Structure of rtyped low level code
by Julian Waters 05 Sep '23

05 Sep '23

Hi all, For fun, I've always wanted to write a translation backend in my own fork of pypy for some time. Is there any resource out there on where to start, for example on how low level rtyped code is structured? best regards, Julian

2 1

Where to begin writing a new translation backend for rpython?
by tanksherman27＠gmail.com 03 Sep '23

03 Sep '23

Hi all, Just for fun, I've always wanted to write a new translation backend for the rpython toolchain. Is there any first tips for doing so (Eg how to translate the output of the rtyped low level graphs to the target language)?

1 0