Issue #14200: Add benchmark results to text flow.

loewis · loewis · commit de157cc5bca4 · 2012-03-06T08:42:17.000+01:00
diff --git a/Doc/whatsnew/3.3.rst b/Doc/whatsnew/3.3.rst
@@ -167,19 +167,16 @@ The storage of Unicode strings now depends on the highest codepoint in the strin
 
 * non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per codepoint.
 
-The net effect is that for most applications, memory usage of string storage
-should decrease significantly - especially compared to former wide unicode
-builds - as, in many cases, strings will be pure ASCII even in international
-contexts (because many strings store non-human language data, such as XML
-fragments, HTTP headers, JSON-encoded data, etc.).  We also hope that it
-will, for the same reasons, increase CPU cache efficiency on non-trivial
-applications.
-
-.. The memory usage of Python 3.3 is two to three times smaller than Python 3.2,
-   and a little bit better than Python 2.7, on a `Django benchmark
-   <http://mail.python.org/pipermail/python-dev/2011-September/113714.html>`_.
-   XXX The result should be moved in the PEP and a link to the PEP should
-   be added here.
+The net effect is that for most applications, memory usage of string
+storage should decrease significantly - especially compared to former
+wide unicode builds - as, in many cases, strings will be pure ASCII
+even in international contexts (because many strings store non-human
+language data, such as XML fragments, HTTP headers, JSON-encoded data,
+etc.).  We also hope that it will, for the same reasons, increase CPU
+cache efficiency on non-trivial applications. The memory usage of
+Python 3.3 is two to three times smaller than Python 3.2, and a little
+bit better than Python 2.7, on a Django benchmark (see the PEP for
+details).
 
 
 PEP 3151: Reworking the OS and IO exception hierarchy
