<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl
<a class="moz-txt-link-rfc2396E" href="mailto:georg@python.org"><georg@python.org></a> wrote:
<blockquote
cite="mid:CAP7+vJJmQPfSi+0++RO6=AG400+OMCyKSe12paLf64Xi41Z8EA@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">In total, almost 500 API items are new or improved in Python 3.3.
For a more extensive list of changes in 3.3.0, see
<a class="moz-txt-link-freetext" href="http://docs.python.org/3.3/whatsnew/3.3.html">http://docs.python.org/3.3/whatsnew/3.3.html</a>
</pre>
</blockquote>
</blockquote>
Reading this to see if I missed anything while downloading the new
release:<br>
<br>
I found:<br>
<blockquote type="cite">For the common user, this change should
result in no visible change in
semantics. Any possible changes required in one’s code to handle
this change
should read the <a class="reference internal"
href="http://docs.python.org/py3k/whatsnew/3.3.html#porting-python-code">Porting
Python code</a> section of this document to see what
needs to be changed, but it will only affect those that currently
manipulate
import or try calling it programmatically.</blockquote>
<br>
Sentence two in this paragraph has bizarre structure, probably due
to being changed from one perspective to another. Suggestion (which
turns out to be briefer):<br>
<br>
For the common user, this change should result in no visible change
in
semantics. Any code changes required are described in the <a
class="reference internal"
href="http://docs.python.org/py3k/whatsnew/3.3.html#porting-python-code">Porting
Python code</a> section of this document; it will only affect code
that currently manipulates
import or calls it programmatically.<br>
</body>
</html>