Mailman 3 October 2019 - pypy-dev

PyPy Winter Sprint + cpyext
by Stefan Beyer 20 Dec '22

20 Dec '22

Hey everyone! Those of you who attended or followed one of the last two winter sprints in Leysin might know me, the others probably won't. I'm (still) a Master's student writing my thesis on PyPy's current issue with cross-heap cycles when using cpyext. The main point is, that they are not collected and stay around as floating garbage, even if they are not reachable any more. Correct me if I'm wrong, but I didn't notice anyone else working on that topic (and/or committing something) since I've picked it up two years ago (yeah, I know, that long ago...). I saw that you would be working on "cpyext performance and completeness" during the current winter sprint this week and thought that this might also concern my thesis. So I thought I'll give you an update. I recently pushed my current (non-optimized, breaking-some-tests, but more or less working) implementation of the "CPython-style" GC-extension for cpyext. It is still in an early stage and not all cases (legacy and non-legacy-finalizers, weakrefs) are handled. However, I picked up some pace during the last couple of weeks and I'm determined to finish this implementation during the following weeks (some quirks with the tests have been haunting me, but I think I figured most of them out by now). After that, I will implement a second alternative implementation (to compare to, mostly for the sake of my thesis), which will take some more time. I also added a couple of fancy test cases (the so called "dot-tests"), so that we can test complex object graphs a little bit easier (and also because it was kind of cool to have another language inside PyPy/RPython, even if it was only for the tests...), with more test cases to come (the current ones are a bit messy). None of the new changes concerning low-latency applications are currently integrated, but that should not be too hard. I guess it won't make much sense for me to join you at this year's winter sprint, especially as I won't be able to get there before Thursday, but I might be able to join you over the IRC channel (or some other form of communication if you like). If there is anything that is worth discussing please let me know! Also feel free to comment on my code, but beware that I might change some things once I try to do some optimizations (probably not many, but at least fix the worst issues) and make it a little bit more readable. You can find my code on the cpyext-gc-cycle branch.<https://bitbucket.org/pypy/pypy/commits/branch/cpyext-gc-cycle> Looking forward to hearing from you! Greetings, Stefan

2 2

PyPy3: is bytecode really incompatible between releases?
by Michał Górny 29 Oct '19

29 Oct '19

Hello, I've noticed that the compiled module suffix keeps changing between PyPy3 releases: it's been .pypy3-71-*.so for 7.1, now it's .pypy3-72- *.so (also .pyc). However, this is a bit surprising to me given that for PyPy2 it's still at .pypy-41.so. Is the bytecode generated by successive PyPy3 releases really incompatible between them? Or are the suffix changes only incidental? They cause quite some trouble for us, since they make it necessary to recompile installed modules on Gentoo, and PyPy's overzealous compiling causes access violations for our users. TIA for any help. -- Best regards, Michał Górny

3 14

contributing to PyPy
by David Kolečkář 16 Oct '19

16 Oct '19

Hello, I would like to ask You, if there is some chance to help with the PyPy project. I am studying MS Computer Sciences at CTU FEE, Prague. Thank You for answer David Koleckar

2 1

P:yPy 7.2 release candidates uploaded, please try them out
by Matti Picus 10 Oct '19

10 Oct '19

I uploaded 7.2.0rc2 tarballs to https://bitbucket.org/pypy/pypy/downloads/ Here are the sha256 hashes: 738df122fd3f202397f6efea641e952214197541f2a0e79112767cd3cfb6eb16 pypy2.7-v7.2.0rc2-aarch64.tar.bz2 53685a718ffb651a82a3fa6de89c8c4229a4a38b358a26100af688aa2eb3e32b pypy2.7-v7.2.0rc2-linux32.tar.bz2 bf8c9a0a0790f77050049c05ac2e66fe09b03f714a613b628bfee91db7e13fb7 pypy2.7-v7.2.0rc2-linux64.tar.bz2 6a9018f38046a51ebe466a5ecde57480b657bf55757669bd3ccb9dabc97652e2 pypy2.7-v7.2.0rc2-osx64.tar.bz2 448ffe6c14df01a0c0a98571731438c78e6165a3959d711e7e5233ba9a44ef81 pypy2.7-v7.2.0rc2-s390x.tar.bz2 4691c4d6566fdcc68ccbb77c1456f004b8749adf397c167472d8b12337291d37 pypy2.7-v7.2.0rc2-src.tar.bz2 2064b6ebd83b809a2a14c34421b63fe6c2a91572502a22e3db06a6dd40bb73c9 pypy2.7-v7.2.0rc2-src.zip 551e8d8cecf78b3892bf0c93fcb24835b9dfb9c0a6a15c37e65f7e775fab7d1b pypy2.7-v7.2.0rc2-win32.zip 5b37cfd78291b336923e87e369c5629390e2143a74f5dee10463ddeac2f35cc8 pypy3.6-v7.2.0rc2-aarch64.tar.bz2 cf0d3421ba0d08f472358d7601fdafce0239b46666fe829b28c77a178c01a719 pypy3.6-v7.2.0rc2-linux32.tar.bz2 96d7274e40cd1e1627b3c29dfda80cb1a1fe22ec3bbc45813ae42b60903b853e pypy3.6-v7.2.0rc2-linux64.tar.bz2 3c2339fc29a6aeb691c52865f44880b30462abd376a4cdf5bbda169594a3bc0d pypy3.6-v7.2.0rc2-osx64.tar.bz2 c4c04c49e707e14c9dbf26847fe2b6ac17271211582ca4f9c8f4785bde2aee51 pypy3.6-v7.2.0rc2-s390x.tar.bz2 a663b6c402b07d3f1598af1836f0573861cba0ce37590b7e3035e5ef8f2186ea pypy3.6-v7.2.0rc2-src.tar.bz2 6be68e337a71152d654da840ca21d0d05a12d6b7727303e6c36b69e93e2bcc76 pypy3.6-v7.2.0rc2-src.zip d1d043d83bfbcb68b94bccbd4eaced8edb285d7f4f52323af481f0f2007e1cdb pypy3.6-v7.2.0rc2-win32.zip If there are no problems I will repackage this commit as the release in a few days Matti

1 0

Re: [pypy-dev] Windows 10 error
by Armin Rigo 09 Oct '19

09 Oct '19

Hi, On Wed, 9 Oct 2019 at 16:45, Kristóf Horváth <horvath.kristof.attila(a)gmail.com> wrote: > Thank you for your reply. The listed dll-s already were parts of my system, but installing Visual C++ Redistributable solved the problem, so it works now. Perhaps, you could write a note about the dependencies onto your installing page. Thanks for the confirmation! I've updated the page http://pypy.org/download.html. A bientôt, Armin

1 0

Windows 10 error
by Kristóf Horváth 09 Oct '19

09 Oct '19

Hello, I downloaded the Windows binary, but pypy3.exe fails on startup with error code 0xc000007b (I tried version 3.6 and 3.5, too). I use Windows 10 x64, can it cause the problem? I read in the building instructions that only a 32-bit version available on Windows at this time, but it should be work on a 64-bit system, right? I couldn't find any useful information about the problem on the internet, have you got any idea what's wrong? Thank you for your help. Regards, Kristóf Horváth

2 2

P:yPy 7.2 release candidates uploaded, please try them out
by Matti Picus 02 Oct '19

02 Oct '19

I uploaded 7.2.0rc tarballs to https://bitbucket.org/pypy/pypy/downloads/ Here are the sha256 hashes: 00b0042d904f1fa1aa5018f5411b8f1715bb7a72ecb5a8193ca8d45dc5754dd6 pypy2.7-v7.2.0rc0-aarch64.tar.bz2 3ab83172ebce4bba3e45c2f583d9419cdb7224cec6eccbb77a49d9377f38cf53 pypy2.7-v7.2.0rc0-linux32.tar.bz2 4e19d649c7442fafe7e342269c3b6da63ebabbb5ee7f5bb0c1a90e351894dff3 pypy2.7-v7.2.0rc0-linux64.tar.bz2 13cbbb8dd7a4cd148b074920b0a69e36828cb14d5a0bf01c0708ec7b3368d5f7 pypy2.7-v7.2.0rc0-osx64.tar.bz2 de8cdce8a35ae9cb48750045e864775752bea30c28096f7209819006d54814f0 pypy2.7-v7.2.0rc0-s390x.tar.bz2 616d66ee4f1020289c57bdc753987d89c0814529196c86f9aac5a51fea05d3f8 pypy2.7-v7.2.0rc0-src.tar.bz2 734a6f4ea1921f533f6ddfb0d07567a9c53389f99f633a965eb4b3ed67ee50ad pypy2.7-v7.2.0rc0-src.zip 9ce3049d40ed136d63ebe5e051899f897aee01dad5a1ffe9bd676fb4c3c6f7ce pypy2.7-v7.2.0rc0-win32.zip 76e16ff998bb1e624942546d5657854eed032fbc27a23d5a7d4eafeada13b059 pypy3.6-v7.2.0rc1-aarch64.tar.bz2 c0505ca984f39cc276584e836e073e7521c4c601890a0634efefff96cbb10bc6 pypy3.6-v7.2.0rc1-linux32.tar.bz2 6046ca5b4adfe7d82cd08128d09bc8cfc808e6da946f47eadf8a88014bed9a34 pypy3.6-v7.2.0rc1-linux64.tar.bz2 b5f28fbb14a3774d7367b5af4f2cf971261c080320f6d6bb91c129ae8e3ccf10 pypy3.6-v7.2.0rc1-osx64.tar.bz2 ecc6bf68b1e2a1d37bdc2534b561bdfcb2a091a329b00f50417aca6456e54847 pypy3.6-v7.2.0rc1-s390x.tar.bz2 810ab3bc7252742c2d18cd07c3ea78f7afedd1693c2195b2f396986809a0c6a6 pypy3.6-v7.2.0rc1-src.tar.bz2 dfb502138069ef2c3865981cc12414052e79b3329791fae8130af232a4f55f42 pypy3.6-v7.2.0rc1-src.zip b08cde67843657497e39c7f6c60774677f43b736e91f79d8707c75652c928c2f pypy3.6-v7.2.0rc1-win32.zip The python3 ones are rc1 since I did not want to move a tag, and I improperly tagged rc0. Please try them out. I already know that we will need to add 38ede7e5cb5a for very large JSON maps, let me know if there are more. Matti

1 0

Migration from Bitbucket to ???
by PIERRE AUGIER 01 Oct '19

01 Oct '19

Hi, I posted this message in https://bitbucket.org/pypy/pypy/issues/3082 but apparently, it's better to post it in this list, so here it is: As explained here https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket, Mercurial features and repositories will be officially removed from Bitbucket and its API on June 1, 2020. I guess you thought about what to do for PyPy repository and PyPy development. I am also a Mercurial user and I am facing the same problem for some repositories. Thus, I am very interested to know what you plan to do. In particular, I am looking for a good forge for the Transonic project (https://transonic.readthedocs.io), which by the way is compatible with PyPy3.6 (currently only the nightly builds) and could help a wider adoption of PyPy3 for projects using the Python scientific stack (just by accelerating the numerical kernels using Numpy and let PyPy accelerate pure Python code). I follow the Heptapod project https://heptapod.net/ (a friendly fork of GitLab to bring very good Mercurial support). It seems to me that it starts to be nearly production ready and that it would nicely fit your workflow with Mercurial. Of course, it would be very convenient if a common instance (free to use for simple users until a certain point) could be setup (something somehow similar to Github, but with Mercurial support). Even for PyPy, it would be good in terms of visibility. I also heard that your repository would have to be fixed to be able to use Heptapod. What is the current status of these issues for PyPy? Have you already decided what to do? Best regards, Pierre -- Pierre Augier - CR CNRS http://www.legi.grenoble-inp.fr LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels BP53, 38041 Grenoble Cedex, France tel:+33.4.56.52.86.16

3 2