With Python 3.2 and even more with Python 3.3, Python 3 became usable for release products. Indeed given the things that are in Python 3 that are not being back-ported to Python 2 (*), using Python 3 should probably be considered mandatory for all Python use. Certainly for new projects, and 2 → 3 ports for all extant codes.

In this session we will investigate some of the issues, especially those relating to handling of concurrency and parallelism, and in particular concurrent.futures. Some material on CSP (**) will almost certainly creep into the session.

A challenge is issued for small codes that can run using Python 2 but not using Python 3.2 or 3.3. BYOCS!

(*) Well even some of these are as third-party packages but we will ignore this. :-)

(**) If you don't know this acronym you will by the end of this session.

	Machine Learning Hands On with F# Tomas Petricek : 13th Jun 2013
	Simplifying Asynchronous Code with Scala Philipp Haller : 5th Jun 2013
	Deuce is (not yet) Emacs under Clojure Hakan Raberg : 4th Jun 2013
	Functional Programming in the enterprise Jon Pither : 3rd Jun 2013
	F# on iPad and iPhone with Xamarin Studi : 30th May 2013
	F# Type Providers Hands On Tomas Petricek : 23rd May 2013
	Be a better developer : 21st May 2013
	Developing Python with PyDev : 21st May 2013
	Machine Learning with Storm + Redis Yodit Stanton : 7th May 2013
	Cascalog for the 80% of Data Science Bruce Durling : 7th May 2013
	F# embedded in Excel Adam Mlocek : 25th Apr 2013
	F# embedded in Excel part 2 Adam Mlocek : 25th Apr 2013
	Pitfalls Of Using Frameworks Paul Brian : 18th Apr 2013
	Adventures with Cython Emil Vaughan : 18th Apr 2013
	Using server management framework, Salt Kris Saxton : 18th Apr 2013