Difference between pages "Key signing" and "Tutorials/Python 3: Making the Leap!"

From LCA2014 Delegate Wiki
(Difference between pages)
Jump to: navigation, search
(Submitting your key)
 
 
Line 1: Line 1:
= Key signing party =
+
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.
We should have a key signing party, up for suggestions on where and when and what format
+
  
 +
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.
  
== Before the event ==
+
== What will be covered? ==
  
You need a gpg key to start, create one now!
+
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.
You might as well make it with as big a key size as possible.
+
<pre>gpg --gen-key
+
gpg --list-secret-keys
+
gpg --fingerprint FA9EC035</pre>
+
  
 +
* 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.
  
== Submitting your key ==
+
We unfortunately won't be able to cover some interesting topics, including
  
Currently nothing has been decided, please add suggestions below.
+
* How to get code to run under python 2 and 3 simultaneously.
* create a wiki page containing your fingerprints
+
* How to port python extension modules.
** [[https://lca2014.linux.org.au/wiki/User:Daniel_sobey Daniel Sobey]]
+
* How to use brand new features which have been introduced in python 3.
* Some other tool, edit this page and we may use it
+
  
{| class="wikitable"
+
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!).
|+ people participating in identification exchange
+
! Real Name !! Key Id !! Key Fingerprint !! Preferred E-mail Address
+
|-
+
  
|-
+
== What to bring ==
| J Random Person  || 0x0000000000000000 || FFFF FFFF FFFF FFFF FFFF  FFFF FFFF FFFF FFFF FFFF || jrp@example.com
+
  
 +
* 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.
| [[https://lca2014.linux.org.au/wiki/User:Mark_Atwood Mark Atwood]]  || 0x5BB3D38332608126 || D37B E0BF 09D3 C69B DDAC  78B5 5BB3 D383 3260 8126 || me@mark.atwood.name
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Daniel_sobey Daniel Sobey]]    ||  0xFA9EC035 || 28F8 2EA3 26A3 7748 EC41  CD28 00D4 08C4 FA9E C035 || dns@dns.id.au
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Daniel_sobey Daniel Sobey]]    ||  0x7E706939 || 9F04 E553 09DA 89A9 44EE  EF41 6D34 FF8A 7E70 6939 || dns@dns.id.au
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Daniel_sobey Daniel Sobey]]    ||  0x2EC08895 || AEAE 53B3 DEE8 1DF9 F28C  A657 86F3 A534 2EC0 8895 || dns@dns.id.au
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Paul_Warren Paul Warren]]  || 0x5341F366208EDB2A ||  DF30 FFE6 CBEE ED60 E340  EEBA 5341 F366 208E DB2A || pwarren@pwarren.id.au, paul@thewarrens.name
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Paul_Warren Paul Warren]]  || 0x89A45B0613ABFE97 ||  2D60 F3A8 CB31 9C99 F76E  0637 89A4 5B06 13AB FE97 || pwarren@pwarren.id.au
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Elizabeth_Krumbach_Joseph Elizabeth Krumbach Joseph]]  || 0x2FC76319BC2349FC || F1A1 2FEF 82A5 666C F9A4  A748 2FC7 6319 BC23 49FC || lyz@princessleia.com
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Arkady_Gundroff Arkady Gundroff]]  || 0x877D7A54 || 27A4 1D27 E9B8 5AD7 1C2A  8A86 ECF8 CCDD 877D 7A54 || rkd@therkd.org
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Arkady_Gundroff Arkady Gundroff]]  || 0x22F75870 || 2D39 1FA0 84A6 AE66 D525  0805 68B2 320E 22F7 5870 || rkd@therkd.org
+
|-
+
| [[https://lca2014.linux.org.au/wiki/User:Kye_Russell Kye Russell]]  || 0xE44FDDE6 || 8AA9 BF1D 306F 1CD6 4D2C  95BA 662A 7109 E44F DDE6 || me@kyerussell.com
+
|-
+
| [[http://www.humbug.org.au/RussellStuart Russell Stuart]] || 0xE7843A8C || D25D D87D F8EA 9ED1 D146  5023 F523 1C62 E784 3A8C || russell-gpg@stuart.id.au<br/>ras@debian.org<br/>russell-debian@stuart.id.au
+
|-
+
| Christopher Yeoh || 0xAAE53307 ||7D5F DD42 C463 D88F 559E  BDF0 3714 8A73 AAE5 3307|| cbkyeoh@gmail.com
+
|-
+
| [[http://www.james.rcpt.to/ James Bromberger]] || 0x9D85C53C || 8591 20FE 0D9F A6A5 B054  C775 AEC8 2874 9D85 C53C || jeb@debia.org<br />jeb@cpan.org<br />james@rcpt.to
+
|-
+
| [[http://www.azabani.com Delan Azabani]] || 0x18416AA7 || 7F21 2455 67B2 3E09 2664  20EF 0548 7476 1841 6AA7 || delan@azabani.com
+
|-
+
| Thomas Chung || 0xB18A274C || 6951 B594 524C E3A9 3734  494F 17E8 091D B18A 274C || thomas@nomology.id.au<br>thomaschung32@gmail.com
+
|-
+
| Karl-Johan Karlsson || 0x331FAE7D || 5893 644B 7783 B5D3 9FD7  F4C6 01BA C4B5 331F AE7D || creideiki@lysator.liu.se<br />creideiki@ferretporn.se
+
|-
+
| Brendan O'Dea || 0xEBDDBB60 || 52D5 B159 3D7F D914 6A5A  6307 1C7C 41ED EBDD BB60 || bod@debian.org
+
|-
+
| Nathan Rickerby || 0xC99822D9 || E123 4567 F324 185C 70B4  DF2C 2542 D563 C998 22D9 || nathan@rickerby.id.au
+
|-
+
| Anibal Monsalve Salazar || 0x947897D8<br>0xACA4350A || C604 5C81 3887 B77C 2DFF  97A5 7C56 ACFE 9478 97D8<br>83C5 0FF1 7534 757A 89D1  6988 0348 02C7 ACA4 350A || anibal@debian.org
+
|-
+
| Jason Lewis || 0x505E764E || B10B 2E72 BB30 FE47 ABC2  F1B9 FA57 1EC7 505E 764E || jason@dickson.st
+
|-
+
| Russell Keith-Magee || 0x37BB5BC3 || CBE7 4366 F6CA 0A0D 4BA7  D2F8 3D2D AB6A 37BB 5BC3 || russell@keith-magee.com
+
|-
+
| Geordie Millar || 0x417605A7 || BB70 1BC9 41C7 09AC FFBD  5E14 8A0F 973C 4176 05A7 || gm@stackunderflow.com
+
|}
+
  
== At the event ==
+
== What to do ==
We will need someone to collate the keys and print them out.
+
Please let us know how many we should print and where to print them.
+
  
What we did last year was go to a lecture theatre with a projector.
+
* Turn up :-)
Each person stands up, shows their photo id and read their fingerprint aloud.
+
* Follow along with all the examples.
printouts of everyone's fingerprints were provided so you can tick off as you go
+
* Try out the techniques on your code as we go.
This worked ok but took a long time to get through everyone.
+
* 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".
  
 +
I look forward to seeing you all for a fun and interesting session.
  
 
+
@timl
== Ad hoc Signing ==
+
 
+
Put your fingerprint on a piece of paper and hand it out to people.
+
No need to do it formally just swap as you meet.
+
 
+
Things to watch out for:
+
* does it match thair name
+
* Does the person have a key with that fingerprint, do the numbers match.
+
* know that anyone can generate a key and claim an email address
+
* if someone can be bothered they can keep trying to generate a key with the first 8 digits the same as another key but getting the whole fingerprint is nearly impossible
+
 
+
 
+
== When you get home ==
+
after the event you should have notes of who to trust the next thing to do is sign the key.
+
You can individually sign each key, export the signature and send it to them.
+
 
+
[https://wiki.debian.org/caff caff] is a tool that automates the signing a little.
+
It will sign and send an email (encrypted if possible) containing the signature.
+
It requires some setup but it does make things easier.
+

Revision as of 18:12, 7 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.

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".

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

@timl