EVE Online Begins the Move to Python 3: The 2.4 Million Line Challenge
Score
71披露了具体代码量、审查要点和潜在替代技术，对关注大规模 Python 迁移的人有较强新增信息。
内容来自知名技术博主 Simon Willison，信息组织清晰，但原始公告本身细节有限。
迁移策略和工具使用对面临类似升级的团队有直接参考价值。
2026 年 8 月刚发布的消息，时效性高。
Simon Willison 是知名且可靠的开发者博主，原始信息来自 EVE Online 官方公告。
Base 79 × T2 Source weight ×0.9 = 71
Curation line 70Selected
Why selected
A significant technical migration by a well-known game company, involving large-scale code handling and Stackless replacement, providing substantial information gain.
AI commentary
「This is a big deal for the Python community: a Stackless Python 2.7 service that has run for twenty years is finally undergoing major surgery. Though no timeline was given, EVE Frontier has already paved the way by replacing Stackless, serving as a pilot run. For teams still on Python 2, this is a valuable real-world roadmap.」
Quick overview
EVE Online has announced the start of its upgrade to Python 3, the first major version migration since moving to Stackless Python 2.7 in 2010. The team will run the futurize script over roughly 2.4 million lines of code, followed by careful manual review of about 20,000 places where Python 2 and 3 behavior differs, such as the integer division semantic change. Since EVE Online still relies on Stackless Python, the announcement does not detail how they plan to replace it, but last year they presented a talk on replacing Stackless in the Carbon engine for their newer game EVE Frontier, using the now open source carbonengine/scheduler library. That may pave the way for this migration.
- EVE Online will run the futurize script over 2.4 million lines of code, followed by manual review of roughly 20,000 compatibility differences.
- The last major upgrade was to Stackless Python 2.7 in 2010, 16 years ago.
- The announcement does not specify how Stackless will be replaced, but EVE Frontier already replaced it using the open-source scheduler library.
- Migration difficulties include Python 2/3 behavior differences, such as `/` returning an integer in Python 2 and a float in Python 3.
Full text
Showing the source text; the full translation is being generated.
EVE Online: The Move to Python 3 Begins!
EVE Online has been one of the most interesting case studies in Python at scale for over twenty years now.They've been running on Stackless Python since their launch in 2003, and their last major upgrade was 16 years ago, to Stackless Python 2.7 in 2010.
Their upgrade to Python 3 will start using the futurize script against 2.4 million lines of code, followed by careful manual review of the ~20,000 places where Python 2 and 3 behavior differ - for example 1 / 2 is 0 in Python 2 but is 0.5 in Python 3.
There's nothing in this announcement about how they plan to replace Stackless, but at their conference last year they presented Scheduling in Carbon: Leaving Stackless Python Behind describing how they replaced Stackless in the Carbon engine for their more recent game EVE Frontier, using their (now open source) carbonengine/scheduler library.
Via Lobster.rs
Tags: eve-online, migrations, python, python3, stackless
Related items
89
FeaturedOpenAI Research: AI Is Redefining Job Boundaries
OpenAI研究：AI正在重新定义工作边界
If you care about the real impact of AI on work, this research is a must-read. Instead of theory, it uses data to show how ChatGPT users expand their task scope, offering direct insights for HR, managers, and every professional looking to upgrade their skills.
87
FeaturedOpenAI CFO Shares Five Lessons for Building an AI-Native Finance Function
OpenAI CFO 分享构建 AI 原生财务职能的五大经验
As an editor, I find this article uniquely valuable because it comes from a finance chief at an AI leader, not an external consultancy, making it highly practical. I recommend it to finance digitalization leads, CFOs, and anyone interested in AI-driven transformation.
87
FeaturedScientific Computing in the Age of Agentic AI: OpenAI Releases New Field Report
智能体AI时代下的科学计算：OpenAI发布新领域报告
This report is one of the most practical analyses in the current AI agent wave, especially suitable for practitioners in computational biology and drug discovery. It answers the key question 'What can AI agents do besides writing code?' and directly demonstrates productivity gains in complex scientific computing.
87
FeaturedReal World VoiceEQ: Measuring the Human Quality of Voice AI
Real World VoiceEQ：量化语音AI的人类自然度
What's noteworthy is that this benchmark truly focuses on the soft metric of 'human-likeness', not traditional speech recognition rate or MOS scores. For teams working on speech synthesis, voice cloning, or voice interaction, this is a highly practical reference tool that quickly identifies model deficiencies in emotion, prosody, etc. However, language support is currently limited; looking forward to future expansion.
85
FeaturedOpenAI Introduces AI Age Scorecard: A New Way to Measure ROI
OpenAI 推出AI时代记分卡：衡量投资回报的新方法
This blog post hits a sore point in the current AI industry: how to quantify input-output. For enterprise decision-makers deploying or planning large-scale AI, it helps avoid herd mentality. My personal advice: try defining 'useful work' based on your own business scenario, and avoid designing metrics that are merely formality.
85
FeaturedHow to Manage AI Investments in the Agentic Era: Focus on Useful Work per Dollar and High-Value Workflows
代理时代如何管理AI投资：聚焦每美元有用功与高价值工作流
This article is especially important for enterprises scaling AI agents. It reminds us that focusing solely on falling API prices is a trap; what really matters is the return per unit of work. I recommend CTOs and CFOs read it together and establish quantitative evaluation mechanisms internally.
85
FeaturedDesigning Organisations That Can Keep Up With AI: Organisational Latency as the Biggest Barrier
设计能跟上AI的组织：组织延迟成为最大障碍
What makes this article truly worth following is that it raises a neglected bottleneck: no matter how strong the technology is, if the organisation can't keep up, it's useless. For CTOs, CIOs, and transformation leaders, this is a more important framework than tech selection.
84
FeaturedRuff v0.16.0 Released: Default Rules Jump from 59 to 413, CI Pipelines Need Attention
Ruff v0.16.0 发布：默认规则从59条激增至413条，CI工作流需关注
For Python developers, this is an unmissable update signal. The significant increase in Ruff's default rules means we can no longer ignore potential issues in our code, and AI fix tools can lower the upgrade cost. Notably, Astral (OpenAI) is deeply integrating AI coding capabilities with static analysis tools, which may become the norm in future engineering practices.