News for hackers. Stuff that matters.
Re:Our Plan for Python 3.13 by sgt on Thursday June 15, 2023 @10:02AM (#36340645)
Not for Python, I feel. In sheer volume, the vast majority of my Python programs are single-threaded. I want my programs to be very quick in runtime when they run.

Those that are multi-threaded are seeing minor to medium load.

If expecting extreme load (like Twitter scale), then Python is usually not the answer (rather go to a statically typed language like Java, Go, Rust etc).

Re:Our Plan for Python 3.13 by gpderetta on Thursday June 15, 2023 @11:05AM (#36341549)
> In sheer volume, the vast majority of my Python programs are single-threaded

obviously if multithreading is near-useless in python, very few programs will take advantage of it.

Re:Our Plan for Python 3.13 by zo1 on Thursday June 15, 2023 @12:10PM (#36342636)
Likewise I can say: Obviously we still have the GIL because very few people want it removed.
Re:Our Plan for Python 3.13 by gpderetta on Friday June 16, 2023 @04:22AM (#36353214)
Well, yes, that's pretty much obvious: the majority of python programmers do not care.

And I'll be first to admit that improving single threaded performance has an higher priority than removing the GIL.

Re:Our Plan for Python 3.13 by AlphaSite on Thursday June 15, 2023 @05:21PM (#36346671)
Is single threaded perf is important, you’ve already lost by using python. You’re only ever going to get, ok-ish performance or slightly more ok-ish
Re:Our Plan for Python 3.13 by gcbirzan on Thursday June 15, 2023 @06:53PM (#36347896)
> Not for Python, I feel. In sheer volume, the vast majority of my Python programs are single-threaded.

Yes, they are single threaded, because using multiple threads brings very little benefit in most cases...

> If expecting extreme load (like Twitter scale), then Python is usually not the answer (rather go to a statically typed language like Java, Go, Rust etc).

So that means we shouldn't get any performance improvements, because there are faster languages out there?