Fighting the Good Fight: Python 3 in your organization
summary
Claim: Facebook goes from "impossible" in 2014 to a majority of Python 3 usage by 2018, with ~55% of entry points and 73% of lines converted, and an internal Python 2 EOL. The work actually done: rebuilt hundreds of wheels, converted Thrift to support Tulip/asyncio, automatic pyflakes linter plus unit tests, changed the build defaults to default to Python 3. Measured wins include 4x CPU and 50% memory on some services; a rewritten infrastructure service ships in production.
AI-written summary · about
chapters (4)
related talks
39mRules for Radicals: Changing the Culture of Python at Facebook
41mYou should switch to Python 3 (two years ago)
27mHow We Migrated 3.8 Million Lines of Python 2 Without Interrupting Deve...
26mPython 2 is dead! Drag your old code into the modern age
26mHow to Succeed with Python Across the Enterprise
36mA Python Takeover
32mHow (not) to upgrade a platform
36mA Python Takeover