Whats the scoop with Python 3?  Paul Barry – Institute of Technology, Carlow in Ireland                   PyCon Ireland 20...
Grab the slides:http://paulbarry.itcarlow.ie/Python3.pdf
Start working with Python 3 now!                     3
It seems nobody was listening...                                   4
So... whats the scoop?                          5
Despite going from strength-to-strength, Python 3 has yet to replace Python 2                                           6
WTF?       7
Despite being nearly 3 years old,Python 3 has yet to replace Python 2                                       8
Thats OK            9
In the short-to-medium term,Python 3 wasnt meant to replace Python 2                                            10
Not yet, anyway...                     11
I wonder are the   coffee refills   free today?                    12
Which version of    Python should I use    today?                   13
Not an either-or decision                            14
What do the good folk at python.org have to say?                                               15
Point #1 - Use 2 instead of 3“... if youre deploying to an environment you dontcontrol, that may impose a specific version...
I recently worked on a project that unashamedly  specified Python 2.6.4 as the target platform   (even though the work was...
Point #2 - Use 2 instead of 3    “... if you want to use a specific third partypackage or utility that doesnt yet have a r...
Another project (wisely) selected Django asthe target web-dev platform... which meant more            work for me in Pytho...
Point #3 - Use 2 instead of 3     “... if you wish to use an alternativeimplementation of Python such as IronPython,      ...
A third project specified the .NET platform, but didnt care which language I used...                                      ...
A third project specified the .NET platform, but didnt care which language I used...  I used IronPython and was restricted...
Its hard to get away from        Python 2...                             23
Its hard to get away from                 Python 2...… especially when Python 2.7 isnt half-bad                           ...
So, like, dude...whats the problem?                      25
Eventually, 2.x wont cut it anymore...                                          26
Python 2.x isDEAD                27
It will soon start to smell                              28
This talks  BIGMESSAGE                29
Your current 2.x codebase is now  LEGACY                                   30
31
32
33
How can you say such a thing?                  34
At some point, youll have to port allof your “current” 2.x code to Python 3                                          35
Python 3 will soon becomeTHE DEFAULT                              36
This Is Your Future:                       37
Imagine if this was to happen with some     other distribution or OS...?!?                                          38
Prevailing attitudes towards Python 3                                        39
Ill just ignore    it and itll    go away.                   40
Ignore the future at your  PERIL                            41
Whatever were they thinking? Sure, the print statement    doesnt even work!!!                               42
The print statement in 2.x isBROKEN                                43
Theres no goodPython 3 specificbooks out there.                    44
45
46
This is all rubbish!   Well just keep                       writing 2.x code                        FOREVER...            ...
You are inDENIAL              48
Be honest... theresnot one single feature  that demands the   upgrade, right?                         49
UNICODE          50
51
Look – we cantdo anything until thoseguys over there update     their code...                          52
Look – we cantdo anything until thoseguys over there update     their code...        I agree - lets                       ...
If you doNOTHING  you are in DENIAL               54
55
56
57
58
Im back where I started                           59
Start working with Python 3 now!                     60
Start your Python 3porting effort now!                      61
Your love lifedepends on it!!!                   62
I really do love you...                          63
Thats nice. But, Idlove you more if onlyyoud port your code    to Python 3.                         64
Final question to those of you that think you can “survive”       with Python 2.x                                 65
How many of you are still supporting       Python 1.x code?                                       66
Questions?             67
Upcoming SlideShare
Loading in...5
×

What's the Scoop with Python 3?

559

Published on

At PyCon Ireland 2010, Paul described his experience of working with Python 3 in creating O'Reilly's Head First Programming and Head First Python (both of which target Python 3). As a big fan of Python 3, Paul suggested that all Python 2 programmers needed to at least try Python 3 as soon as was practical, if not embrace it for all "new" work. In this talk, Paul provides an update on the current status of Python 3 and discusses the community's adoption (or lack of) the latest version of the Python programming language, talking about what has changed in the year and a bit since last year, as well as describing his own experience of working with Python on recent consultancy projects.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
559
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

What's the Scoop with Python 3?

  1. 1. Whats the scoop with Python 3? Paul Barry – Institute of Technology, Carlow in Ireland PyCon Ireland 2011 1
  2. 2. Grab the slides:http://paulbarry.itcarlow.ie/Python3.pdf
  3. 3. Start working with Python 3 now! 3
  4. 4. It seems nobody was listening... 4
  5. 5. So... whats the scoop? 5
  6. 6. Despite going from strength-to-strength, Python 3 has yet to replace Python 2 6
  7. 7. WTF? 7
  8. 8. Despite being nearly 3 years old,Python 3 has yet to replace Python 2 8
  9. 9. Thats OK 9
  10. 10. In the short-to-medium term,Python 3 wasnt meant to replace Python 2 10
  11. 11. Not yet, anyway... 11
  12. 12. I wonder are the coffee refills free today? 12
  13. 13. Which version of Python should I use today? 13
  14. 14. Not an either-or decision 14
  15. 15. What do the good folk at python.org have to say? 15
  16. 16. Point #1 - Use 2 instead of 3“... if youre deploying to an environment you dontcontrol, that may impose a specific version rather than allowing you a free selection from the available versions.” 16
  17. 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) 17
  18. 18. Point #2 - Use 2 instead of 3 “... if you want to use a specific third partypackage or utility that doesnt yet have a released version that is compatible with Python 3, and porting that package is a non-trivial task...” 18
  19. 19. Another project (wisely) selected Django asthe target web-dev platform... which meant more work for me in Python 2.x 19
  20. 20. Point #3 - Use 2 instead of 3 “... if you wish to use an alternativeimplementation of Python such as IronPython, Jython or PyPy...” 20
  21. 21. A third project specified the .NET platform, but didnt care which language I used... 21
  22. 22. A third project specified the .NET platform, but didnt care which language I used... I used IronPython and was restrictedto working with the 2.7 release of Python 22
  23. 23. Its hard to get away from Python 2... 23
  24. 24. Its hard to get away from Python 2...… especially when Python 2.7 isnt half-bad 24
  25. 25. So, like, dude...whats the problem? 25
  26. 26. Eventually, 2.x wont cut it anymore... 26
  27. 27. Python 2.x isDEAD 27
  28. 28. It will soon start to smell 28
  29. 29. This talks BIGMESSAGE 29
  30. 30. Your current 2.x codebase is now LEGACY 30
  31. 31. 31
  32. 32. 32
  33. 33. 33
  34. 34. How can you say such a thing? 34
  35. 35. At some point, youll have to port allof your “current” 2.x code to Python 3 35
  36. 36. Python 3 will soon becomeTHE DEFAULT 36
  37. 37. This Is Your Future: 37
  38. 38. Imagine if this was to happen with some other distribution or OS...?!? 38
  39. 39. Prevailing attitudes towards Python 3 39
  40. 40. Ill just ignore it and itll go away. 40
  41. 41. Ignore the future at your PERIL 41
  42. 42. Whatever were they thinking? Sure, the print statement doesnt even work!!! 42
  43. 43. The print statement in 2.x isBROKEN 43
  44. 44. Theres no goodPython 3 specificbooks out there. 44
  45. 45. 45
  46. 46. 46
  47. 47. This is all rubbish! Well just keep writing 2.x code FOREVER... 47
  48. 48. You are inDENIAL 48
  49. 49. Be honest... theresnot one single feature that demands the upgrade, right? 49
  50. 50. UNICODE 50
  51. 51. 51
  52. 52. Look – we cantdo anything until thoseguys over there update their code... 52
  53. 53. Look – we cantdo anything until thoseguys over there update their code... I agree - lets do nothing. 53
  54. 54. If you doNOTHING you are in DENIAL 54
  55. 55. 55
  56. 56. 56
  57. 57. 57
  58. 58. 58
  59. 59. Im back where I started 59
  60. 60. Start working with Python 3 now! 60
  61. 61. Start your Python 3porting effort now! 61
  62. 62. Your love lifedepends on it!!! 62
  63. 63. I really do love you... 63
  64. 64. Thats nice. But, Idlove you more if onlyyoud port your code to Python 3. 64
  65. 65. Final question to those of you that think you can “survive” with Python 2.x 65
  66. 66. How many of you are still supporting Python 1.x code? 66
  67. 67. Questions? 67
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×