EVE Online Embarks on Historic Python 3 Migration to Modernize Two Decades of Space Simulation Code
For more than twenty years, the expansive science-fiction universe of EVE Online has operated on a foundational code architecture rooted in the early 2000s. Every digital vessel, player-driven corporation, and multi-thousand-participant battle in the single-shard MMORPG has relied on Python 2. Specifically, the game’s core mechanics have depended upon a custom-built, highly modified variant of Stackless Python—an alternate implementation of the CPython interpreter optimized for lightweight concurrency and cooperative multitasking.
However, technological evolution waits for no software project. With the upstream Stackless Python interpreter having halted development at version 3.8 and officially reaching archival status last year, CCP Games has initiated a monumental engineering initiative: migrating the entire 2.4-million-line codebase of EVE Online to Python 3.12.
This technological transition represents one of the most complex software refactoring challenges in the history of online gaming. Unlike single-player titles or segmented server-based games that can be taken offline for days or weeks during major overhauls, EVE Online demands continuous uptime. The universe must remain operational, player assets must be preserved, and the simulated player-driven economy cannot afford catastrophic interruptions.
The Architectural Roots of EVE Online and Stackless Python
When development on EVE Online began in the late 1990s, CCP Games sought a programming language that could accelerate development speed, lower entry barriers for engineering and design teams, and handle complex simulation logic efficiently. Python offered the ideal balance of readability and power.
To achieve the massive concurrency required for thousands of players interacting within a single shared universe, CCP adopted Stackless Python. Unlike standard CPython, Stackless removes the traditional C call stack, utilizing "tasklets" instead. This architectural choice predated modern asynchronous paradigms like async/await, providing EVE with a robust mechanism to run thousands of sequential operations concurrently without blocking the main server threads.
Over the decades, however, maintaining a heavily customized, non-standard interpreter created significant technical debt. The custom codebase required dedicated internal engineering resources simply to keep the interpreter compatible with modern operating systems, security patches, and hardware architectures, such as Apple Silicon. Furthermore, developers were cut off from the broader Python ecosystem—unable to leverage modern package managers, type hinting frameworks, or performance improvements introduced in newer versions of the language.
The Pilot Phase: Lessons from EVE Frontier
Before committing the primary EVE Online production servers to the Python 3 transition, CCP Games tested the waters with EVE Frontier, a newer survival-focused title sharing structural DNA and underlying technology with the flagship MMORPG. Led by principal programmers and platform architects, including Thomas Dähling, the engineering team used EVE Frontier as a testbed for the Carbon technology stack’s transition out of Python 2.7.
This proving ground allowed CCP Games to identify unforeseen memory corruption issues, native extension incompatibilities, and behavioral discrepancies between the language versions. For instance, updating native C++ extensions to interface correctly with a modern CPython runtime exposed lingering memory layout shifts that had remained dormant since the Python 2.3 era.
Following the successful integration of Python 3 into EVE Frontier, the company gained the confidence and tooling necessary to tackle the much larger, highly mature EVE Online production environment.
Breaking Down the Migration: Code, Math, and Memory
Migrating 2.4 million lines of production code while the live environment hums along is a delicate balancing act. Jamie Bannister, an engineer with sixteen years of experience on EVE Online who is currently spearheading the migration project, notes that the process requires addressing three primary obstacles: runtime code syntax, mathematical precision, and state persistence.
Syntax and the Legacy-to-2.7 Bridge
The initial phase of the project involved systematically upgrading ancient idioms—some dating back to Python 2.4 and 2.5—into syntax that is fully compatible with modern Python standards while maintaining temporary 2.7 execution capability. Utilizing automated refactoring scripts such as Futurize, the team addressed thousands of deprecated patterns, such as replacing dictionary .has_key() method calls with the native in operator. According to internal metrics, syntactic compliance for Python 3 was elevated from 94 percent to 99.8 percent ahead of the hard fork.
The Mathematics of Division
One of the most critical challenges lies in mathematical discrepancies between Python 2 and Python 3. In Python 2, dividing two integers resulted in integer division (truncating decimals), whereas Python 3 performs true floating-point division. Within EVE Online, approximately 6,500 lines of core logic—ranging from weapon damage calculations and shield mitigations to navigation vectors—rely on these mathematical outcomes. Allowing unchecked division changes to propagate through the simulation could silently alter combat outcomes, economic valuations, and physics simulations across the universe. Engineers must manually review and adjust these calculations to ensure historical continuity in game mechanics.
The 100-Gigabyte Pickle Dilemma
Perhaps the most daunting logistical challenge involves state persistence. EVE Online relies heavily on serialized Python objects—colloquially known as "pickles"—to store persistent game data, including the long-term memory states of Non-Player Characters (NPCs) such as mission-giving agents. Across two decades of operation, roughly 100 gigabytes of pickled Python objects have accumulated within the database infrastructure.
Because standard SQL queries cannot deserialize Python bytecode, and because memory layouts change fundamentally between major interpreter versions, CCP Games cannot execute a simple database migration script. The engineering team is actively developing specialized conversion pipelines to ingest these legacy data structures and translate them into standardized, version-independent formats like Protocol Buffers, ensuring that historical NPC memories and player asset states survive the upgrade intact.
Deployment Strategy: The Mixed-Mode Horizon
Rather than executing a single, high-risk "big bang" deployment where the entire cluster of roughly 200 server nodes and tens of thousands of client installations switch to Python 3 simultaneously, CCP Games is adopting a phased rollout strategy.
The team is constructing a "mixed mode" deployment architecture. This system will allow individual nodes within the server cluster—and selectively, client instances—to operate on Python 3 while interfacing with remaining Python 2 components through robust serialization shims and translation layers. By decentralizing the risk, engineers can isolate potential regressions, monitor performance metrics under live player loads, and progressively phase out legacy infrastructure without scheduling prolonged server downtime.
Industry Implications and Broader Impact
The EVE Online Python 3 migration stands as a landmark case study in enterprise software longevity. Most commercial software applications are rewritten from scratch or deprecated long before reaching a 20-year operational milestone. By choosing to refactor an immense, highly specialized codebase in place, CCP Games is preserving a historically significant digital ecosystem.
Beyond securing the game’s immediate operational future against unpatched security vulnerabilities and dropping OS support, the migration unlocks modern developer tooling. Integrating type-checking frameworks, linters, and standard packaging pipelines will streamline internal development workflows, reduce onboarding friction for new engineering hires, and position the game’s proprietary Carbon technology stack to benefit from ongoing CPython performance optimizations.
As the migration advances through its unstable testing branches toward live server integration, the global EVE Online community watches closely. For an MMORPG where virtual destruction is permanent and the stakes of the simulated economy are notoriously high, the invisible plumbing of the software stack has never mattered more. Through meticulous planning, automated linting, and incremental deployment, CCP Games is ensuring that humanity’s most ambitious space simulator will continue undocking into the digital frontier for years to come.
