[pypy-commit] extradoc extradoc: updates

arigo pypy.commits at gmail.com
Fri Sep 23 16:29:37 EDT 2016


Author: Armin Rigo <arigo at tunes.org>
Branch: extradoc
Changeset: r5710:acd514577bc1
Date: 2016-09-23 22:29 +0200
http://bitbucket.org/pypy/extradoc/changeset/acd514577bc1/

Log:	updates

diff --git a/planning/py3.5/cpython-crashers.rst b/planning/py3.5/cpython-crashers.rst
--- a/planning/py3.5/cpython-crashers.rst
+++ b/planning/py3.5/cpython-crashers.rst
@@ -74,3 +74,10 @@
 * ceval.c: GET_AITER: calls _PyCoro_GetAwaitableIter(), which might
   get an exception from calling the user-defined __await__() or checking
   what it returns; such an exception is completely eaten.
+
+* while I'm at it, this is an old issue that was forgotten twice on the
+  issue tracker: ``class C: __new__=int.__new__`` and ``class C(int):
+  __new__=object.__new__`` can each be instantiated, even though they
+  shouldn't.  This is because ``__new__`` is completely ignored if it is
+  set to a built-in function that uses ``tp_new_wrapper`` as its C code.
+  This is true for most or all the built-in types' ``__new__``.
diff --git a/planning/py3.5/milestone-1-progress.rst b/planning/py3.5/milestone-1-progress.rst
--- a/planning/py3.5/milestone-1-progress.rst
+++ b/planning/py3.5/milestone-1-progress.rst
@@ -14,6 +14,8 @@
 * richard: extended slicing for memory view
 * richard: bytes % args, bytearray % args: PEP 461
 
+* arigo: faulthandler module
+
 
 
 Misc stuff not formally in any milestone


More information about the pypy-commit mailing list