time for a new release: rc2
I have uploaded rc2 of pypy v7.3.2 to https://buildbot.pypy.org/pypy/ (note the trailing slash) The hashes are here https://foss.heptapod.net/pypy/pypy.org/-/blob/branch/default/pages/download... The release note is here https://doc.pypy.org/en/latest/release-v7.3.2.html This release does include a 3.7 alpha. Please try them out, especially on windows (extra points for non-english interfaces and install paths) and macos (extra points for machines that run without homebrew stuff installed), to make sure you can run your project with them. Any comments are welcome. Since the rc1 candidates, we have updated the stdlibs of 3.6 and 2.7 for various upstream issues and CVEs, and fixed an issue with rpython on ARM. Thanks to all who helped test and fix. 3.7 now uses stdlib 3.7.9. Matti
On Wed, 2020-09-16 at 16:56 +0300, Matti Picus wrote:
Ok, I've done some thorough testing today. PyPy2.7 looks all good. PyPy3.6 has some test failures, including 2 that are not on buildbot but that's not a regression from previous version. PyPy3.7 has lots of test failures, too many for me to compare against buildbot. I've also tested PyPy3.7 against a set of ~200 packages. Two specific problems came up: 1. attrs and zope.interface both fail tests with the following exception: zope.interface.exceptions.InvalidInterface: Concrete attribute, __orig_bases__ 2. hypothesis fails tests with asyncio error: Traceback (most recent call last): File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/tests/cover/test_async_def.py", line 33, in test_foo @given(st.text()) File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/build/lib/hypothesis/core.py", line 1145, in wrapped_test raise the_error_hypothesis_found File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/tests/cover/test_async_def.py", line 30, in execute_example asyncio.run(f()) File "/usr/lib/pypy3.7/lib-python/3/asyncio/runners.py", line 39, in run loop = events.new_event_loop() File "/usr/lib/pypy3.7/lib-python/3/asyncio/events.py", line 762, in new_event_loop return get_event_loop_policy().new_event_loop() File "/usr/lib/pypy3.7/lib-python/3/asyncio/events.py", line 660, in new_event_loop return self._loop_factory() File "/usr/lib/pypy3.7/lib-python/3/asyncio/unix_events.py", line 51, in __init__ super().__init__(selector) File "/usr/lib/pypy3.7/lib-python/3/asyncio/selector_events.py", line 54, in __init__ super().__init__() File "/usr/lib/pypy3.7/lib-python/3/asyncio/base_events.py", line 370, in __init__ self._clock_resolution = time.get_clock_info('monotonic').resolution TypeError: time() takes 0 positional arguments but 1 was given -- Best regards, Michał Górny
On Wed, 2020-09-16 at 16:56 +0300, Matti Picus wrote:
Ok, I've done some thorough testing today. PyPy2.7 looks all good. PyPy3.6 has some test failures, including 2 that are not on buildbot but that's not a regression from previous version. PyPy3.7 has lots of test failures, too many for me to compare against buildbot. I've also tested PyPy3.7 against a set of ~200 packages. Two specific problems came up: 1. attrs and zope.interface both fail tests with the following exception: zope.interface.exceptions.InvalidInterface: Concrete attribute, __orig_bases__ 2. hypothesis fails tests with asyncio error: Traceback (most recent call last): File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/tests/cover/test_async_def.py", line 33, in test_foo @given(st.text()) File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/build/lib/hypothesis/core.py", line 1145, in wrapped_test raise the_error_hypothesis_found File "/tmp/portage/dev-python/hypothesis-5.35.3/work/hypothesis-hypothesis-python-5.35.3/hypothesis-python-pypy3/tests/cover/test_async_def.py", line 30, in execute_example asyncio.run(f()) File "/usr/lib/pypy3.7/lib-python/3/asyncio/runners.py", line 39, in run loop = events.new_event_loop() File "/usr/lib/pypy3.7/lib-python/3/asyncio/events.py", line 762, in new_event_loop return get_event_loop_policy().new_event_loop() File "/usr/lib/pypy3.7/lib-python/3/asyncio/events.py", line 660, in new_event_loop return self._loop_factory() File "/usr/lib/pypy3.7/lib-python/3/asyncio/unix_events.py", line 51, in __init__ super().__init__(selector) File "/usr/lib/pypy3.7/lib-python/3/asyncio/selector_events.py", line 54, in __init__ super().__init__() File "/usr/lib/pypy3.7/lib-python/3/asyncio/base_events.py", line 370, in __init__ self._clock_resolution = time.get_clock_info('monotonic').resolution TypeError: time() takes 0 positional arguments but 1 was given -- Best regards, Michał Górny
participants (2)
-
Matti Picus -
Michał Górny