1
What's the scoop with Python 3?
Paul Barry – Institute of Technology, Carlow in Ireland
PyCon Ireland 2011
Grab the slides:
http://paulbarry.itcarlow.ie/Python3.pdf
3
Start working withPython 3 now!
4
It seems nobody was listening...
5
So... what's the scoop?
6
Despite going from strength-to-strength,Python 3 has yet to replace Python 2
7
WTF?
8
Despite being nearly 3 years old,Python 3 has yet to replace Python 2
9
That's OK
10
In the short-to-medium term,Python 3 wasn't meant to replace Python 2
11
Not yet, anyway...
12
I wonder are thecoffee refillsfree today?
13
Which version ofPython
should I usetoday?
14
Not an either-or decision
15
What do the good folk at python.org have to say?
16
“... if you're deploying to an environment you don't control, that may impose a specific version rather
than allowing you a free selection from the available versions.”
Point #1 - Use 2 instead of 3
17
I recently worked on a project that unashamedly specified Python 2.6.4 as the target platform
(even though the work was XML-based)
18
“... if you want to use a specific third party package or utility that doesn't yet have a released
version that is compatible with Python 3, and porting that package is a non-trivial task...”
Point #2 - Use 2 instead of 3
19
Another project (wisely) selected Django asthe target web-dev platform... which meant more
work for me in Python 2.x
20
“... if you wish to use an alternative implementation of Python such as IronPython,
Jython or PyPy...”
Point #3 - Use 2 instead of 3
21
A third project specified the .NET platform,but didn't care which language I used...
22
A third project specified the .NET platform,but didn't care which language I used...
I used IronPython and was restrictedto working with the 2.7 release of Python
23
It's hard to get away fromPython 2...
24
It's hard to get away fromPython 2...
… especially when Python 2.7 isn't half-bad
25
So, like, dude... what's the problem?
26
Eventually, 2.x won't cut it anymore...
27
Python 2.x is
DEAD
28
It will soon start to smell
29
This talk's
BIGMESSAGE
30
Your current 2.x codebase is now
LEGACY
31
32
33
34
How can you saysuch a thing?
35
At some point, you'll have to port allof your “current” 2.x code to Python 3
36
Python 3 will soon become
THE DEFAULT
37
This Is Your Future:
38
Imagine if this was to happen with someother distribution or OS...?!?
39
Prevailing attitudes towards Python 3
40
I'll just ignoreit and it'llgo away.
41
Ignore the future at your
PERIL
42
Whatever were they thinking?Sure, the print statement
doesn't even work!!!
43
The print statement in 2.x is
BROKEN
44
There's no goodPython 3 specific books out there.
45
46
47
This is all rubbish! We'll just keepwriting 2.x code
FOREVER...
48
You are in
DENIAL
49
Be honest... there'snot one single feature
that demands theupgrade, right?
50
UNICODE
51
52
Look – we can'tdo anything until thoseguys over there update
their code...
53
Look – we can'tdo anything until thoseguys over there update
their code... I agree - let'sdo nothing.
54
If you do
NOTHINGyou are in
DENIAL
55
56
57
58
59
I'm back where I started
60
Start working withPython 3 now!
61
Start your Python 3porting effort now!
62
Your love lifedepends on it!!!
63
I really do love you...
64
That's nice. But, I'dlove you more if onlyyou'd port your code
to Python 3.
65
Final question to those of youthat think you can “survive”
with Python 2.x
66
How many of you are still supportingPython 1.x code?
67
Questions?
Recommended
