Python 3.11 vs 3.10 performance

Post by uoaei » Wed, Jul 06, 2022, 6:06 PM UTC

upupandup wrote: post #80

bilsbie wrote: post #53

I’d be curious to see the speed up compared to python 2.4. To see how far it’s come since I first got started with it.

it means you are not following PEP8 if you get non descriptive errors, it means you haven't followed proper exception handling/management its not the fault of Python but the developer. go ahead and downvote me but you if you mentioned parent's comment in an interview, you would not receive a call back or at least I hope the interviewer is realizing the skill gap.

Post by gary_0 » Wed, Jul 06, 2022, 6:09 PM UTC

gostsamo wrote: post #68

uniqueuid wrote: post #2

These speedups are awesome, but of course one wonders why they haven't been a low-hanging fruit over the past 25 years. Having read about some of the changes [1], it seems like the python core committers preferred clean over fast implementations and have deviated from this mantra with 3.11. Now let's get a sane concurrency story (no multiprocessing / queue / pickle hacks) and suddenly it's a completely different lang…

A few people tried to excuse the slow python, but as far as I know the story, excuses are not necessary. Truth is that python was not meant to be fast, its source code was not meant to be fast, and its design was not optimized with the idea of being fast. Python was meant as a scrypting language that was easy to learn and work with on all levels and the issue of its slowness became important when it outgrew its role…

Post by dekhn » Wed, Jul 06, 2022, 6:09 PM UTC

LtWorf wrote: post #191

dekhn wrote: post #139

Earlier quoted context omitted.

If I remember correctly iron python ran on mono it just didn't have all of the .net bits. I remember at the python conference when it was introduced he actually showed how you could bring up clippy or a wizard programmatically from python talking directly to the operating system through its native apis. Really the value came from the thread safe container/collections data types which are the foundation of high perfor…

Too bad .net is designed for windows and on linux the APIs feel like windows API that kinda sorta work on linux.

Post by bufferoverflow » Wed, Jul 06, 2022, 6:10 PM UTC

woodruffw wrote: post #16

tasubotadas wrote: post #8

Cool improvement but changes very little when Python is x100 times slower than other GC languages.

This is probably the wrong comparison to make: Python is two orders of magnitude slower than compiled GC languages, but it's in the same order of magnitude as most other interpreted GC languages. (It actually changes a whole lot, because there's a whole lot of code already out there written in Python. 25% faster is still 25% faster, even if the code would have been 100x faster to begin with in another language.)

Post by mikepurvis » Wed, Jul 06, 2022, 6:14 PM UTC

teekert wrote: post #161

bilsbie wrote: post #55

Earlier quoted context omitted.

When is that coming? Yes the error messages are confusing in a big list comprehension.

Whenever I nest a list comprehension I feel dirty anyway, I wonder if a better error message will help solve something that is just hard to grasp sometimes.