A Future Python

Transcript

1. a Python future

2. Armin @mitsuhiko Ronacher

3. None

4. what can I tell you?

5. let me tell you about a future

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

   here is what I wish it to become

7. and the future will be different

8. None

9. where are we now?

10. and how we came here

11. people love python

12. stackoverflow most loved

13. stackoverflow most wanted

14. but what about the future?

15. let's make a detour

16. None
17. None
18. None

19. rust is hard

20. rust is complex

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

    mean for Python?)

22. the packaging story

23. the distribution story

24. reliability and trust

25. zero cost abstractions

26. a clear backwards compatibility story

27. the community

28. rust tells us a story

29. rust's values are transparent

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. it's okay to create something complex

32. if using it is easy

33. our approach so far

34. we succeed despite our process

35. the wider community vs the core developers

36. the packaging story

37. distribution

38. typing

39. why?

40. we're afraid of complexity

41. we work against each other

42. how do we prevent this from happening?

43. we need to work together

44. not to be afraid

45. we need a vision

46. and that vision could be bold

47. working groups?

48. pay developers?

49. embrace black and lint name violations?

50. TypeScript for Python?

51. py_modules and package.json?

52. non indexable UTF-8 strings?

53. phase out cabi for ffi?

54. load wasm modules?

55. strip stdlib down?

56. multi version import system?

57. simplify object model?

58. cross compile to wasm?

59. 0

60. Q&A lucumr.pocoo.org / @mitsuhiko