A Future Python

181de1fb11dffe39774f3e2e23cda3b6?s=47 Armin Ronacher
October 05, 2018
Programming
0
1.6k

A Future Python

A presentation about how Python could be.

181de1fb11dffe39774f3e2e23cda3b6?s=128

Armin Ronacher

October 05, 2018
Tweet

Want more?

181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
0
140
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
0
130
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
5
650
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
9
510
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
1
260
766b9746b59e6f09e280cd33cf4ed419?s=48 skipperchong
0
170
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
6
320
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
6
220
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
3
300
C35e01544a0dd94a2cf1619ee8a42ebb?s=48 clairelew
4
560
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
1
170
B3ace07412a5178ea778e7eec161fc0a?s=48 jcasabona
4
250

Transcript

  1. 1.

    a Python future

  2. 2.

    Armin @mitsuhiko Ronacher

  3. 3.
    None
  4. 4.

    what can I tell you?

  5. 5.

    let me tell you about a future

  6. 6.

    i can't tell you what the future will be, but

    here is what I wish it to become
  7. 7.

    and the future will be different

  8. 8.
    None
  9. 9.

    where are we now?

  10. 10.

    and how we came here

  11. 11.

    people love python

  12. 12.

    stackoverflow most loved

  13. 13.

    stackoverflow most wanted

  14. 14.

    but what about the future?

  15. 15.

    let's make a detour

  16. 16.
    None
  17. 17.
    None
  18. 18.
    None
  19. 19.

    rust is hard

  20. 20.

    rust is complex

  21. 21.

    so why do people love Rust? (and what does it

    mean for Python?)
  22. 22.

    the packaging story

  23. 23.

    the distribution story

  24. 24.

    reliability and trust

  25. 25.

    zero cost abstractions

  26. 26.

    a clear backwards compatibility story

  27. 27.

    the community

  28. 28.

    rust tells us a story

  29. 29.

    rust's values are transparent

  30. 30.

    […] the Rust programming language is fundamentally about empowerment: no

    matter what kind of code you are writing now, Rust empowers you to reach farther, to program with confidence in a wider variety of domains than you did before.
  31. 31.

    it's okay to create something complex

  32. 32.

    if using it is easy

  33. 33.

    our approach so far

  34. 34.

    we succeed despite our process

  35. 35.

    the wider community vs the core developers

  36. 36.

    the packaging story

  37. 37.

    distribution

  38. 38.

    typing

  39. 39.

    why?

  40. 40.

    we're afraid of complexity

  41. 41.

    we work against each other

  42. 42.

    how do we prevent this from happening?

  43. 43.

    we need to work together

  44. 44.

    not to be afraid

  45. 45.

    we need a vision

  46. 46.

    and that vision could be bold

  47. 47.

    working groups?

  48. 48.

    pay developers?

  49. 49.

    embrace black and lint name violations?

  50. 50.

    TypeScript for Python?

  51. 51.

    py_modules and package.json?

  52. 52.

    non indexable UTF-8 strings?

  53. 53.

    phase out cabi for ffi?

  54. 54.

    load wasm modules?

  55. 55.

    strip stdlib down?

  56. 56.

    multi version import system?

  57. 57.

    simplify object model?

  58. 58.

    cross compile to wasm?

  59. 59.

    0

  60. 60.

    Q&A lucumr.pocoo.org / @mitsuhiko