T
Theo
Russel Winder gives numerous reasons why now is the time for you to switch to Python 3 RIGHT NOW!
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 consideredmandatory 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.
Sign up for the free evening event here - http://skillsmatter.com/podcast/java-jee/switch-to-python-3-now-immediately
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 consideredmandatory 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.
Sign up for the free evening event here - http://skillsmatter.com/podcast/java-jee/switch-to-python-3-now-immediately