Downloaded 181 times
Uploaded byRichard Jones
State of Python (2010)
The document provides an overview of Python's development history, highlighting key releases from its inception in 1989 through various updates until January 2010. It covers significant features introduced in versions 3.0 and 3.1, including changes to print functions, exception handling, and new standard library modules. Additionally, it discusses the migration efforts for various libraries and frameworks, as well as community initiatives and upcoming Python web developments.
More Related Content
Similar to State of Python (2010)
State of Python (2010)
- 1. State of Python January, 2010 Richard Jones richard@python.org
- 2.
- 3. Some History • Development started December, 1989
- 4. Some History • Development started December, 1989 • 0.9.0 released February, 1991
- 5. Some History • Development started December, 1989 • 0.9.0 released February, 1991 • 1.5.2 released April, 1999
- 6. Some History • Development started December, 1989 • 0.9.0 released February, 1991 • 1.5.2 released April, 1999 • 2.0 released October, 2000
- 7. Some History • Development started December, 1989 • 0.9.0 released February, 1991 • 1.5.2 released April, 1999 • 2.0 released October, 2000 • py3k branched & PEP 3000 March, 2006
- 8. Some History • Development started December, 1989 • 0.9.0 released February, 1991 • 1.5.2 released April, 1999 • 2.0 released October, 2000 • py3k branched & PEP 3000 March, 2006 • 3.0 released November 25, 2008
- 9. Some History • Development started December, 1989 • 0.9.0 released February, 1991 • 1.5.2 released April, 1999 • 2.0 released October, 2000 • py3k branched & PEP 3000 March, 2006 • 3.0 released November 25, 2008 • 3.1 released June 27th, 2009
- 10.
- 11. What’s New In3.13.0
- 12. What We Utterly BrokeIn 3.0 With No Regard For The Consequences
- 13.
- 14. What’s New In3.0 • print() and exec() are still functions
- 15. What’s New In3.0 • print() and exec() are still functions • dict.keys(), dict.items(), dict.values(), map(), filter() and zip() still return iterators
- 16. What’s New In3.0 • print() and exec() are still functions • dict.keys(), dict.items(), dict.values(), map(), filter() and zip() still return iterators • text is still unicode and files still read bytes
- 17. What’s New In3.0 • print() and exec() are still functions • dict.keys(), dict.items(), dict.values(), map(), filter() and zip() still return iterators • text is still unicode and files still read bytes • as, with, True, False and None are still keywords
- 18.
- 19. What’s New In3.0 • exception chaining is still there
- 20. What’s New In3.0 • exception chaining is still there • the standard library is still better-organised
- 21.
- 22. What’s New In3.0 • old-style classes are still gone
- 23. What’s New In3.0 • old-style classes are still gone • cmp(), reduce(), apply(), coerce(), callable() and raw_input() are still the way of the dodo
- 24. What’s New In3.0 • old-style classes are still gone • cmp(), reduce(), apply(), coerce(), callable() and raw_input() are still the way of the dodo • `` and <> are also still gone
- 25. What’s New In3.0 • old-style classes are still gone • cmp(), reduce(), apply(), coerce(), callable() and raw_input() are still the way of the dodo • `` and <> are also still gone • string exceptions are still no more
- 26. What’s New In3.0 / 2.6
- 27. What’s New In3.0 / 2.6 • multiprocessing
- 28. What’s New In3.0 / 2.6 • multiprocessing • io and json
- 29. What’s New In3.0 / 2.6 • multiprocessing • io and json • tkinter.ttk (new complementary widgets, styling through “style sheets”)
- 31. What’s New In3.0 / 2.6
- 32. What’s New In3.0 / 2.6 • advanced string formatting
- 33. What’s New In3.0 / 2.6 • advanced string formatting • Abstract Base Classes (and function annotation in 3.0)
- 34. What’s New In3.0 / 2.6 • advanced string formatting • Abstract Base Classes (and function annotation in 3.0) • 0o21 == 17 0b1101 == 13
- 35. What’s New In3.0 / 2.6 • advanced string formatting • Abstract Base Classes (and function annotation in 3.0) • 0o21 == 17 0b1101 == 13 • Class decorators
- 36. What’s New In3.0 / 2.6
- 37. What’s New In3.0 / 2.6 • added numbers, fractions, cmath, ssl modules
- 38. What’s New In3.0 / 2.6 • added numbers, fractions, cmath, ssl modules • new toys in math, functools, itertools, collections
- 39.
- 40. What’s New In3.1 • python can execute packages (and zip files)
- 41. What’s New In3.1 • python can execute packages (and zip files) • unittest supports skipping tests
- 42. What’s New In3.1 • python can execute packages (and zip files) • unittest supports skipping tests • sys.version_info is a named tuple >>> sys.version_info sys.version_info(major=3, minor=1, micro=1, releaselevel='final', serial=0)
- 43. What’s New In3.1 • python can execute packages (and zip files) • unittest supports skipping tests • sys.version_info is a named tuple >>> sys.version_info sys.version_info(major=3, minor=1, micro=1, releaselevel='final', serial=0) • improved Python 2 pickle support
- 44. What’s New In3.1 / 2.7
- 45. What’s New In3.1 / 2.7 • thanks David Gay: >>> 1.1 1.1000000000000001 becomes... >>> 1.1 1.1
- 46. What’s New In3.1 / 2.7 • thanks David Gay: >>> 1.1 1.1000000000000001 becomes... >>> 1.1 1.1 • still doesn’t make this correct: 1.1 + 2.2 = 3.3
- 47. What’s New In3.1 / 2.7
- 48. What’s New In3.1 / 2.7 • io & json rewritten in C
- 49. What’s New In3.1 / 2.7 • io & json rewritten in C • memoryview object (mutable byte array)
- 50. What’s New In3.1 / 2.7 • io & json rewritten in C • memoryview object (mutable byte array) • ordered dictionary
- 51.
- 52. What’s New In3.1 STILL B0RKS UR CODEZ!
- 53. Books • Python 3for Absolute Beginners by Tim Hall and J-P Stacey • Programming in Python 3 (Second Edition) by Mark Summerfield
- 54. Books • Dive IntoPython 3 by Mark Pilgrim Python 3 Patterns, Recipes and Idioms by Bruce Eckel and Friends
- 55. Books • Invent YourOwn Computer Games with Python (Second Edition) by Albert Sweigart
- 56. Other Books in2009 • IronPython in Action by Michael Foord
- 57. Other Books in2009 • Head First Programming by Paul Barry and David Griffiths • Python for Software Design: How to Think Like a Computer Scientist by Allen B. Downey
- 58. Other Books in2009 • Gray Hat Python: Python Programming for Hackers and Reverse Engineers by Justin Seitz • Hello World! Computer Programming for Kids and Other Beginners by Warren Sande and Carter Sande
- 60.
- 61. Python 2.7 • expectedin June - alpha 2 out now
- 62. Python 2.7 • expectedin June - alpha 2 out now • includes backporting from 3.1
- 63. Python 2.7 • expectedin June - alpha 2 out now • includes backporting from 3.1 • will be the last 2.x release
- 64.
- 65. IronPython • Runs onthe .NET CLR
- 66. IronPython • Runs onthe .NET CLR • 2.6 released December 2009
- 67. IronPython • Runs onthe .NET CLR • 2.6 released December 2009 • Visual Studio integration higher priority than IronPython 3
- 68.
- 69. Jython • Python compiledto the Java VM
- 70. Jython • Python compiledto the Java VM • 2.5.1 released September 2009
- 71. Jython • Python compiledto the Java VM • 2.5.1 released September 2009 • target CPython 2.7 for next major release
- 72. PyPy • Python inPython • Michael Hudson will talk about that
- 73.
- 74. Migration Progress • SQLAlchemy(so db layers too)
- 75. Migration Progress • SQLAlchemy(so db layers too) • Distribute (was “setuptools”)
- 76. Migration Progress • SQLAlchemy(so db layers too) • Distribute (was “setuptools”) • pygame reloaded (pgreloaded)
- 77. Migration Progress • SQLAlchemy(so db layers too) • Distribute (was “setuptools”) • pygame reloaded (pgreloaded) • Django (mostly done)
- 78. Migration Progress • SQLAlchemy(so db layers too) • Distribute (was “setuptools”) • pygame reloaded (pgreloaded) • Django (mostly done) • numpy has a plan http://www.scipy.org/Python3k
- 79.
- 80.
- 81. Migration Progress • http://wiki.python.org/moin/PortingPythonToPy3k •python-porting mailing list http://mail.python.org/mailman/listinfo/python-porting
- 82. Migration Progress • http://wiki.python.org/moin/PortingPythonToPy3k •python-porting mailing list http://mail.python.org/mailman/listinfo/python-porting • a bunch of very useful reference code http://code.google.com/p/python-incompatibility/
- 84. 2to3c • an implementationof Python's 2to3 for C code
- 85. 3to2 • GSoC project •http://bitbucket.org/amentajo/lib3to2/
- 86. Language Moratorium Temporary suspensionof all changes to the Python language syntax, semantics, and built-ins for a period of at least two years from the release of Python 3.1
- 87.
- 88.
- 89. Python 3 speedup •Unladen Swallow to be merged into py3k (Google’s efforts to speed up Python)
- 90. Python 3 speedup •Unladen Swallow to be merged into py3k (Google’s efforts to speed up Python) • A more rational GIL
- 91.
- 92. Community • Kiwi PyCon(woot)
- 93. Community • Kiwi PyCon(woot) • planet.python.org
- 94. Community • Kiwi PyCon(woot) • planet.python.org • www.python-forum.org/pythonforum
- 95. Community • Kiwi PyCon(woot) • planet.python.org • www.python-forum.org/pythonforum • PyPI comments
- 96.
- 97.
- 98.
- 99. Skulpt • http://www.skulpt.org/ • entirelyin-browser implementation of Python
- 100. Skulpt • http://www.skulpt.org/ • entirelyin-browser implementation of Python • No preprocessing, plugins, or server-side support required
- 101. Shed Skin 0.3 •Python-to-C++ compiler • improved type inference • support for 'map', 'filter', 'reduce', the 'with' statement • many more library modules supported • several important optimizations
- 102. tinypy • cython, pyrex •tinpy → C++ → XCode → iPhone
- 103. Distribute & pip •replaces setuptools and easy_install • Distribute compatible with python 3 ... pip soon
- 104.
- 105. Web Stuff • Django1.2 on the way (alpha Jan 2010) (full Python 3 support in a year or so)
- 106. Web Stuff • Django1.2 on the way (alpha Jan 2010) (full Python 3 support in a year or so) • TurboGears 2.1 coming (2.0 was June 2009)
- 107. Web Stuff • Django1.2 on the way (alpha Jan 2010) (full Python 3 support in a year or so) • TurboGears 2.1 coming (2.0 was June 2009) • CherryPy 3.1.2 in April 2009 3.2 due out soon supports Python 3
- 108. Web Stuff • Django1.2 on the way (alpha Jan 2010) (full Python 3 support in a year or so) • TurboGears 2.1 coming (2.0 was June 2009) • CherryPy 3.1.2 in April 2009 3.2 due out soon supports Python 3 • Pylons 0.9.7 in February 2009 Python 3 support (Pylons 1.1) mid-2010?
- 109. Web Stuff • 6thPlone Conf 2009 • 2nd DjangoCon 2009 • Django Ski 2010
- 111.
- 112. virtualenv • stand-alone pythonenvironments
- 113. virtualenv • stand-alone pythonenvironments • with or without system extensions
- 114. virtualenv • stand-alone pythonenvironments • with or without system extensions • use it!
Editor's Notes
- #3 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #4 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #5 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #6 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #7 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #8 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #9 so a good place to start is &#x201C;what&#x2019;s new in 3.1&#x201D;
- #10 an even better place is to maybe recap what 3.0 gave us
- #11 or, as some sections of the media and Slashdot reported ...
- #12 I think we can all remember where we were on that fateful day when Google just stopped working when 3.0 was released. Oh, those were the days.
- #17 urllib/urllib2 -> urllib (package); httplib/cookielib/BaseHTTPServer(etc) -> http.client, http.server; anydbm/dbhash/gdbm/etc -> dbm; xmlrpclib/SimpleXMLRPCServer -> xmlrpc; also PEP 8 changes (ConfigParser -> configparser)
- #18 urllib/urllib2 -> urllib (package); httplib/cookielib/BaseHTTPServer(etc) -> http.client, http.server; anydbm/dbhash/gdbm/etc -> dbm; xmlrpclib/SimpleXMLRPCServer -> xmlrpc; also PEP 8 changes (ConfigParser -> configparser)
- #23 also in 2.6 (note &#x201C;T&#x201D;kinter)
- #24 also in 2.6 (note &#x201C;T&#x201D;kinter)
- #25 also in 2.6 (note &#x201C;T&#x201D;kinter)
- #27 you can get a bunch of the 3.0 features in 2.6 using __future__ (eg. unicode literals)
- #28 you can get a bunch of the 3.0 features in 2.6 using __future__ (eg. unicode literals)
- #29 you can get a bunch of the 3.0 features in 2.6 using __future__ (eg. unicode literals)
- #30 you can get a bunch of the 3.0 features in 2.6 using __future__ (eg. unicode literals)
- #31 math: inf, -inf, nan, factorial, inverse hyperbolic functions and a bunch of others functools: reduce() itertools: cartesian product of iterables, combinations, permutations collections: namedtuple, deque enhancements, ABCs for Iterable and Mappings
- #32 math: inf, -inf, nan, factorial, inverse hyperbolic functions and a bunch of others functools: reduce() itertools: cartesian product of iterables, combinations, permutations collections: namedtuple, deque enhancements, ABCs for Iterable and Mappings
- #49 hackers, reverse engineers debuggers, torjans, fuzzers, emulators, code/library injection, sniffing, ...
- #50 warning with the code download
- #51 (2 enters maintenance mode) To reassure people on this, 2.5.5 has just been released.
- #52 (2 enters maintenance mode) To reassure people on this, 2.5.5 has just been released.
- #53 (2 enters maintenance mode) To reassure people on this, 2.5.5 has just been released.
- #57 - 2.5 already supports some of CPython 2.6&#x2019;s features (eg. class decorators) - the backported 3.1 features in 2.7 aid 3.1 compatibility - unicode by default helps IronPython and Jython
- #58 - 2.5 already supports some of CPython 2.6&#x2019;s features (eg. class decorators) - the backported 3.1 features in 2.7 aid 3.1 compatibility - unicode by default helps IronPython and Jython
- #59 - 2.5 already supports some of CPython 2.6&#x2019;s features (eg. class decorators) - the backported 3.1 features in 2.7 aid 3.1 compatibility - unicode by default helps IronPython and Jython
- #61 some big-name projects are done, some not so much posgresql but not mysql, even pl/python in psql supports 2&3
- #62 some big-name projects are done, some not so much posgresql but not mysql, even pl/python in psql supports 2&3
- #63 some big-name projects are done, some not so much posgresql but not mysql, even pl/python in psql supports 2&3
- #64 some big-name projects are done, some not so much posgresql but not mysql, even pl/python in psql supports 2&3
- #65 some big-name projects are done, some not so much posgresql but not mysql, even pl/python in psql supports 2&3
- #72 - due to last for entire 3.3 release cycle - Slow things down for a while to: 1. Let py3k settle for a while, 2. Let alternative implementations catch up - It&#x2019;s not because &#x201C;we&#x2019;re done&#x201D;
- #73 Old GIL: ticks; multi-core systems degenerated badly New GIL: time (5ms by default) multi-core performance unaffected (still only one thread at a time though)
- #74 Old GIL: ticks; multi-core systems degenerated badly New GIL: time (5ms by default) multi-core performance unaffected (still only one thread at a time though)
- #75 Old GIL: ticks; multi-core systems degenerated badly New GIL: time (5ms by default) multi-core performance unaffected (still only one thread at a time though)
- #85 The goal of cython could be described as providing an easy way to convert a Python module into a C extension.
- #87 Django 1.2: multiple databases, improved CSRF, configurable email backends, messaging framework, smarter &#x201C;if&#x201D; tag, localization improvement, and a ton of other stuff
- #88 Django 1.2: multiple databases, improved CSRF, configurable email backends, messaging framework, smarter &#x201C;if&#x201D; tag, localization improvement, and a ton of other stuff
- #89 Django 1.2: multiple databases, improved CSRF, configurable email backends, messaging framework, smarter &#x201C;if&#x201D; tag, localization improvement, and a ton of other stuff
- #90 Django 1.2: multiple databases, improved CSRF, configurable email backends, messaging framework, smarter &#x201C;if&#x201D; tag, localization improvement, and a ton of other stuff
- #91 Django Ski - Whistler, 2-4 March 2010