Rules for Radicals: Changing the Culture of Python at Facebook
summary
Tells how Python 3 becomes the default at Facebook by shipping concrete infrastructure: Thrift Python 3 support lands (Feb 2014), hundreds of third‑party modules are rebuilt or made 2/3‑polyglot, and a new fpkg rewrite is implemented in Python 3; an automatic pyflakes linter runs under both 2 and 3 and unit tests run on both to block regressions. Default flips May 2016; Python 3 pars grow from ~4% to ~10% and asyncio runs on hundreds of thousands of machines.
AI-written summary · about
chapters (11)
- 0:00Introduction to Facebook culture
- 1:36Dependency management with Par
- 3:27The state of Python 3 in 2013
- 7:08Initiating Python 3 migration
- 10:48Rewriting fpkg in Python 3
- 14:32Enforcing compliance through linting
- 17:20Streamlining adoption
- 20:01Cultural shift via education
- 24:18Making Python 3 the default
- 27:48Key takeaways for change
- 28:58Q&A and closing remarks
related talks
26mRULES FOR RADICALS: CHANGING THE CULTURE OF PYTHON
31mFighting the Good Fight: Python 3 in your organization
43mPython 3: ten years later
41mYou should switch to Python 3 (two years ago)
31mPython 3 for People Who Haven't Been Paying Attention
01h 12mPython 3: the Next Generation (is here already)
32mHow (not) to upgrade a platform
26mPython 2 to 3: How to Upgrade and What Features to Start Using