How to Succeed with Python Across the Enterprise
summary
Bloomberg claims Python adoption grows to 3,000 engineers after an intern wraps key C++ libraries, enabling cross-application use; a two-person infrastructure team (started 2016) evolves into a global unit that ships packaged C++ bindings, replaces the unruly extended interpreter, and stabilizes deployment and upgrade processes. Guilds coordinate meetups, docs, and inner-source work; most packages enter maintenance mode and the open-sourced memory diagnostic tool proves effective in production.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 0:40About Bloomberg
- 1:23Bloomberg in movies
- 1:54History of C
- 3:07Why Python
- 3:36Three Pillars
- 4:11Community Interest
- 4:58Intern Project
- 6:37Technical support
- 7:08Technical objectives
- 8:01Community issues
- 8:53Dependency management
- 9:46Python community
- 10:43Guidelines for participation
- 11:21Team challenges
- 12:43Communication
- 13:36Documentation
- 14:15Extended Interpreter
- 14:50C Libraries
- 15:43First Release
- 16:21First Class Language
- 17:10Community Driven Projects
- 18:26Meetings
- 18:43Team
- 19:19The Python Guild
- 19:42Maintenance mode
- 20:24Package changes
- 21:13Cultivating guilts
- 21:48Colocation
- 22:20Upgrade Life Cycle
- 22:53Community
- 24:03Memory
- 24:30PythonCon
- 25:12Questions
related talks
53mPython strategy panel
41mHow to Grow an Open Source Project: A Case Study of Python
30mEmpowered by Python - A success story
25mHow to bring your C++ project to Python land
14mPython powered people: Teaching non-tech professionals to code
29mIs Python ready for the Enterprise?
31mFighting the Good Fight: Python 3 in your organization
43mPython 3: ten years later