On Mon, Jun 7, 2010 at 4:27 PM, Antoine Pitrou <span dir="ltr">&lt;<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

<div class="im">
&gt; I am not<br>
&gt; aware of anything added since 2.5 that isn&#39;t backported or previously<br>
&gt; available as a separate library (I&#39;m sure there&#39;s *something*, just nothing<br>
&gt; I can think of).<br>
<br>
</div><br>Really, I&#39;m too lazy to go and read the changelogs, but there<br>
definitely are many improvements that are not available in Python 2.5<br>
and older.<br>
<div class="im"><br>
&gt; There is no clear policy about how backports are managed.<br>
<br>
</div>That&#39;s because, contrary to what you seem to think, external backports<br>
are the exception and not the rule.<br></blockquote></div><br>I offered examples, you were too lazy to read the changelogs, your sweeping declaration does not seem justified.<br><br>From What&#39;s New in Python 2.6:<br>

<br>contextlib: attached to a language feature.<br>multiprocessing: backported<br>new string formatting: though a method, it&#39;d be easy to produce in a module form.  I&#39;m not aware of a backport.<br>abstract base classes: I don&#39;t think this can be backported wouldn&#39;t all kinds of contortions<br>

ast: associated with the implementation/language<br>json: backported (implicitly, as it is simplejson)<br>plistlib: I&#39;m guessing this was added to support packaging.  It exists separately.<br><br>What&#39;s New in Python 2.7:<br>

argparse: implicitly backported<br>changes to logging: not sure what will happen with this; the module has been backported in the past<br>memoryview: not aware of it being backported<br>importlib: technically including it in 2.7 is a backport, but otherwise no<br>

ttk: appears to be backported (<a href="http://pypi.python.org/pypi/pyttk/">http://pypi.python.org/pypi/pyttk/</a>)<br>unittest: backported<br>ElementTree: backported<br><br>Digging deeper into 2.5:<br>functools: apparently backported at one time, now defunct<br>

ctypes: the backport appears to be dead<br>sqlite3: actively developed (different name?)<br>wsgiref: backported<br>hashlib: backported<br><br>Every release there&#39;s some additions to collections, which have not been backported.<br>

<br>So in summary, of 17 additions which seemed &quot;backportable&quot; to me (not counting 3 modules that seemed tied to language features):<br>* 4 were not backported<br>* 3 have defunct or ambiguous backports<br>
* 10 were backported<br><br>-- <br>Ian Bicking  |  <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>