aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarl Friedrich Bolz-Tereick <cfbolz@gmx.de>2022-02-18 12:41:05 +0100
committerCarl Friedrich Bolz-Tereick <cfbolz@gmx.de>2022-02-18 12:41:05 +0100
commit8af180e4f6e700963cf13aa1c76c5a5dc719330f (patch)
tree0a7cc737793f82012b79f5a8304d239363bfde3b
parentupdate the release note (diff)
downloadpypy-8af180e4f6e700963cf13aa1c76c5a5dc719330f.tar.gz
pypy-8af180e4f6e700963cf13aa1c76c5a5dc719330f.tar.bz2
pypy-8af180e4f6e700963cf13aa1c76c5a5dc719330f.zip
fix link, the trace issue is a bit more general
-rw-r--r--pypy/doc/release-v7.3.8.rst8
1 files changed, 5 insertions, 3 deletions
diff --git a/pypy/doc/release-v7.3.8.rst b/pypy/doc/release-v7.3.8.rst
index 862e723cb4..c3fe571f70 100644
--- a/pypy/doc/release-v7.3.8.rst
+++ b/pypy/doc/release-v7.3.8.rst
@@ -116,13 +116,15 @@ releases for those platforms.
Known Issues with PyPy3.9
=========================
+
- There is still a known `speed regression`_ around ``**kwargs`` handling
- We slightly modified the concurrent future's ``ProcessExcecutorPool`` to
start all the worker processes when the first task is recieved (like on
Python3.8) to avoid an apparent race condition when using ``fork`` and
threads (issue 3650_).
-- Some of the code trace reporting with ``pypy -m trace --trace`` is slightly
- off. See issues 3673_ and 3674_.
+- There are sime issues with line tracing using ``sys.settrace``, traced lines
+ can be slightly off in some rare situations. This can affect code coverage
+ reporting. See issues 3673_ and 3674_.
Changelog
=========
@@ -322,4 +324,4 @@ Python 3.8 C-API
.. _bpo43522: https://bugs.python.org/issue43522
.. _bpo35545: https://bugs.python.org/issue35545
.. _errcheck: https://docs.python.org/3/library/ctypes.html#ctypes._FuncPtr.errcheck
-.. _`speed regression`_: https://foss.heptapod.net/pypy/pypy/-/issues/3649
+.. _`speed regression`: https://foss.heptapod.net/pypy/pypy/-/issues/3649