[Python-ideas] Moving development out of the standard library

Ian Bicking ianb at colorstudy.com
Tue Jun 8 00:16:17 CEST 2010


On Mon, Jun 7, 2010 at 4:27 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:

>  > I am not
> > aware of anything added since 2.5 that isn't backported or previously
> > available as a separate library (I'm sure there's *something*, just
> nothing
> > I can think of).
>
>
> Really, I'm too lazy to go and read the changelogs, but there
> definitely are many improvements that are not available in Python 2.5
> and older.
>
> > There is no clear policy about how backports are managed.
>
> That's because, contrary to what you seem to think, external backports
> are the exception and not the rule.
>

I offered examples, you were too lazy to read the changelogs, your sweeping
declaration does not seem justified.

>From What's New in Python 2.6:

contextlib: attached to a language feature.
multiprocessing: backported
new string formatting: though a method, it'd be easy to produce in a module
form.  I'm not aware of a backport.
abstract base classes: I don't think this can be backported wouldn't all
kinds of contortions
ast: associated with the implementation/language
json: backported (implicitly, as it is simplejson)
plistlib: I'm guessing this was added to support packaging.  It exists
separately.

What's New in Python 2.7:
argparse: implicitly backported
changes to logging: not sure what will happen with this; the module has been
backported in the past
memoryview: not aware of it being backported
importlib: technically including it in 2.7 is a backport, but otherwise no
ttk: appears to be backported (http://pypi.python.org/pypi/pyttk/)
unittest: backported
ElementTree: backported

Digging deeper into 2.5:
functools: apparently backported at one time, now defunct
ctypes: the backport appears to be dead
sqlite3: actively developed (different name?)
wsgiref: backported
hashlib: backported

Every release there's some additions to collections, which have not been
backported.

So in summary, of 17 additions which seemed "backportable" to me (not
counting 3 modules that seemed tied to language features):
* 4 were not backported
* 3 have defunct or ambiguous backports
* 10 were backported

-- 
Ian Bicking  |  http://blog.ianbicking.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20100607/04a733d0/attachment.html>


More information about the Python-ideas mailing list