Some basic sample code for stackless python, for those like me who had never heard of it: https://github.com/stackless-dev/stacklessexamples/blob/main...

Say "stackless tasklet" five times fast.

Can an experienced player gives us a summary of what's the "vibe" of the EVE online community these days? I was lightly involved ~15 years ago.

> So how do you migrate 2.4 million lines of code?

> Very carefully, and in multiple stages.

That answer is so 3 months ago

1/2 troll side-galley comment: use AI and translate to Rust.

If the outcome or outputs / test cases are known, AI is great at language translations.

Stackless python had such potential, it could be extremely useful in Agent era for long running tasks with durable state.

modern Python went in a somewhat different direction with asyncio, but with tasklet and continuation it could be a much powerful combo.

> 50 uses of <>, a way of writing "not equal" so old that many working Python developers have never seen it.

This hit me. Not sure when this was used and was deprecated.

I shouldn't be surprised, given I saw plenty of nicely functioning legacy codebases, but still, somehow this isn't the news I was expecting to hear in 2026.

If I were Fenris Creations, I would make a copy of Allegiance

https://en.wikipedia.org/wiki/Allegiance_%28video_game%29

It really speaks to how great the technical team can be. As crazy as it sounds Goldman Sacks and JP Morgan both maintained 2.7 Python as a core language until just a few years ago (yes, it's still used in production).

> The classic example is division: in Python 2, 1 / 2 is 0; while in Python 3 it is 0.5.

Can someone kindly explain this?

edit: I misread it as “In Python 2 2.1/2 is 0, while in Python 3 it is 0.5”

What happened with the stackless python? Did they get rid of all the stackless stuff?

When python started incorporating asyncio my initial reaction was fairly negative. I was behaving like a grumpy graybeard programmer ("kids these days should learn how to use concurrency instead of working on a new runtime altogether!" [0]).

But after using it for a production project I have to say I'm deeply satisfied and surprised by the maturity, quality of APIs and performance in general.

I was proven wrong and I'm happy about that :)

[0] Old man yell at clouds type of meme

It's kinda funny to read a headline like this in 2026

the eve client is pretty incredibly well made these days. but when the server side solution was to exponentially reduce time , i think they fundamentally lost somewhere else. maybe something good will come out of (some?) that server c++ code being released as well

I thought I was a Python 2.7 holdout for a long time.

> Some of you may remember upgrading to Stackless Python 2.5 in 2007, then to Stackless Python 2.7 in 2010. That was the last time EVE changed its Python version.

Yikes. 2010 ... python is built forever.

But, ignoring this - I think when the "scripting" languages can bridge the speed penalty towards C, even if not reaching it for many reasons, then they become real contenders here.

Had to check the date.

Eve Online used to be great.

Is there anything similarly great around now?

They also open sourced their game engine? https://news.ycombinator.com/item?id=48780387 https://www.gamesindustry.biz/eve-onlines-carbon-engine-is-n...

I wish there was a test instance people were allowed to play around on. I never did it but for a while the game client wasn't really secure & you could just talk to the python repl basically, and script the game. I think that would be an incredible experience all unto its own, to teach coding, to be an interesting experience. Feels like with Carbon being open source, there's need for just a little more to get back around to that halycon moment.

Seems to me like a migration that should have been done 15 years ago.

This feels suspiciously AI-authored

what did they do about stackless? are they using greenlet or did they switch to asyncio?

googled it so this becomes a PSA: https://simonwillison.net/2026/Aug/25/eve-online-move-to-pyt...

so it's neither, it's their own: https://github.com/carbonengine/scheduler

so that's interesting

[dead]

[flagged]

[flagged]

The proposed solution to 2.4M lines of python is.. more python, with the primary motivation being "performance" lol