Difference between pages "Lightning Talks" and "Tutorials/Python 3: Making the Leap!"

From LCA2014 Delegate Wiki
(Difference between pages)
Jump to: navigation, search
 
 
Line 1: Line 1:
This year the lightning talks are being held on Wednesday morning after the Official Opening. There may be a second session on Friday during the closing session.
+
On Wednesday at 10:40 in the Robert Street Lecture Theatre I will be running a tutorial on porting code written for python 2 to work in python 3.
  
The rules will be the same a for Brisbane in 2011:
+
This session will be live and interactive, so to get the most out of the tutorial, please bring along a laptop and be ready to hack.
  
1. Talks are for 90 seconds.
+
== What will be covered? ==
  
2. You must put your name and topic on the wiki page if you want to present.
+
Getting code to run on python 3 is a *massive* topic, and we could spend an entire week looking at it and not cover everything. As we only have 100 minutes we will only cover a relatively small, but IMHO important, subset of the topic. In particular, we will look at.
  
3. If you want to use a set of slides, these must be in a pdf file either emailed to bunyipr@gmail.com by 8:30 on Wednesday or provided on a usb flash drive by 9am. There is absolutely no guarantee your slides will be synchronised with your talk or shown at all so have a 'Plan B'!
+
* How to get code which currently runs under 2.7 to run under 3.3 (without maintaining 2.7 backwards compatibility).
 +
* How to modify your 2.7 code to be as close to 3.3 compatible as possible.
 +
* How to use different tools to automate the porting process.
 +
* Common gotchas with the automated tools which may require manual intervention
 +
* Strategies for using all the different tools and techniques to make the porting process as simple as possible.
  
4. The video of your talk and slides will be published under a Creative Commons, By Attribution license.
+
We unfortunately won't be able to cover some interesting topics, including
  
If you wish to give a talk, please put your name and presentation title in the list below. Format as a sequential number, your name, Title of Presentation.
+
* How to get code to run under python 2 and 3 simultaneously.
Presentation filename should be in the following format nn_FirstName_Lastname.pdf where nn is the sequential number below.
+
* How to port python extension modules.
 +
* How to use brand new features which have been introduced in python 3.
  
Thanks,
+
The session will cater to a fairly broad range of abilities. If you're a python newbie, you should be able to keep up with everything. If you're a python guru you might just learn something new (I know I did while preparing the session!).
  
Stephen.
+
== What to bring ==
  
'''List of proposals'''
+
* A laptop with python 2 and python 3 installed.
* 01, Stephen Boyd, Some issues storing passwords.
+
* A shell and text editor.
* 02, Bianca Gibson, PyLadies Australia
+
* Any python code which you'd like help porting form 2 to 3.
* 03, Brianna Laugher, Crowdfunding free software
+
* The example code from github: https://github.com/timleslie/LCA_py2to3
* 04, Tim Ansell, slidelint - Making your slides awesome.
+
 
* 05, Alan Robertson - Some experiences in raising GeekGirls
+
All examples are platform agnostic and should work on linux/osx/windows.
* 06, Arjen Lentz, BlueHackers @ lca2014
+
 
* 07, Arjen Lentz, RepRap based Curriculum
+
== What to do ==
* 08, Tom Eastman, Announcing Kiwi PyCon 2014
+
 
* 09, Michael Borthwick, A read only filesystem for the Raspberry Pi
+
* Turn up :-)
* 10, Clinton Roy, Announcing PyCon Australia 2014
+
* Follow along with all the examples.
* 11, Michael Still, My toothbrush has a serial number
+
* Try out the techniques on your code as we go.
 +
* Ask questions if you would like clarification...
 +
* ... but understand that the answer might be "that's beyond the scope of this session, come and chat with me later".
 +
* Edit this wiki! If you have questions or know of relevant resources, please share them on this page for the benefit of all over the week.
 +
* If we get to the end of the session and you have questions or want to chat about anything, please come and say hi :-)
 +
 
 +
I look forward to seeing you all for a fun and interesting session.
 +
 
 +
@timl
 +
 
 +
= FAQ =
 +
 
 +
EDIT ME! If you have a question you'd like more details on, feel free to list it here.
 +
 
 +
= Resources =
 +
 
 +
EDIT ME! If you know of a useful resource for python 2 to 3 porting, please add it here.
 +
 
 +
* [http://docs.python.org/2/library/2to3.html 2to3 docs]
 +
* [http://docs.python.org/3/whatsnew/3.0.html What's new in 3.0]
 +
* [http://www.python.org/dev/peps/pep-3108/ Standard Library Changes]
 +
* [http://docs.python.org/3/howto/pyporting.html Porting 2 to 3 by Brett Cannon]
 +
* [http://docs.python.org/2/using/cmdline.html#cmdoption-3 The -3 command line option]
 +
* [http://docs.python.org/3/howto/cporting.html Porting extension modules to python 3]
 +
* [http://www.python.org/dev/peps/pep-3105/ Print as a function]

Latest revision as of 12:06, 8 January 2014

On Wednesday at 10:40 in the Robert Street Lecture Theatre I will be running a tutorial on porting code written for python 2 to work in python 3.

This session will be live and interactive, so to get the most out of the tutorial, please bring along a laptop and be ready to hack.

Contents

What will be covered?

Getting code to run on python 3 is a *massive* topic, and we could spend an entire week looking at it and not cover everything. As we only have 100 minutes we will only cover a relatively small, but IMHO important, subset of the topic. In particular, we will look at.

  • How to get code which currently runs under 2.7 to run under 3.3 (without maintaining 2.7 backwards compatibility).
  • How to modify your 2.7 code to be as close to 3.3 compatible as possible.
  • How to use different tools to automate the porting process.
  • Common gotchas with the automated tools which may require manual intervention
  • Strategies for using all the different tools and techniques to make the porting process as simple as possible.

We unfortunately won't be able to cover some interesting topics, including

  • How to get code to run under python 2 and 3 simultaneously.
  • How to port python extension modules.
  • How to use brand new features which have been introduced in python 3.

The session will cater to a fairly broad range of abilities. If you're a python newbie, you should be able to keep up with everything. If you're a python guru you might just learn something new (I know I did while preparing the session!).

What to bring

  • A laptop with python 2 and python 3 installed.
  • A shell and text editor.
  • Any python code which you'd like help porting form 2 to 3.
  • The example code from github: https://github.com/timleslie/LCA_py2to3

All examples are platform agnostic and should work on linux/osx/windows.

What to do

  • Turn up :-)
  • Follow along with all the examples.
  • Try out the techniques on your code as we go.
  • Ask questions if you would like clarification...
  • ... but understand that the answer might be "that's beyond the scope of this session, come and chat with me later".
  • Edit this wiki! If you have questions or know of relevant resources, please share them on this page for the benefit of all over the week.
  • If we get to the end of the session and you have questions or want to chat about anything, please come and say hi :-)

I look forward to seeing you all for a fun and interesting session.

@timl

FAQ

EDIT ME! If you have a question you'd like more details on, feel free to list it here.

Resources

EDIT ME! If you know of a useful resource for python 2 to 3 porting, please add it here.