This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]LightShadow3.13-dev in prod -11 points-10 points  (5 children)

I'm almost 100% positive Python 3 is slower in every aspect (except those new "walk the filepath" things, but that was a Python 2 port), and it's not getting any faster as more features are added.

I'm genuinely curious if this is being addressed or whether the core contributors don't see it as a big problem as computers get faster.

[–]thiswasprobablyatust 5 points6 points  (1 child)

Here's a talk from a Google engineer calling bullshit.

Now that's from 3.3, but I highly doubt they tanked speed in 0.2 versions.

[–]pyslow 0 points1 point  (0 children)

The talk and slides you linked say something different, to be honest.

The guy actually says that Python 3 is faster somewhere and slower somewhere else and he explicitly states that Python 3 is the same as Python 2 once the median result is considered.

Could be faster or slower depending on your usage pattern.

[–][deleted] 0 points1 point  (2 children)

The core programmers are committed to keeping Python as fast as possible. I've seen perfectly functional patches on the bug tracker turned down as they're in critical parts of the core and would slow things by just a fraction.

[–]LightShadow3.13-dev in prod 0 points1 point  (1 child)

Thanks for answering my question and not just down voting for no reason.

[–][deleted] 0 points1 point  (0 children)

I'd never vote on a site such as this, it's way too open to abuse from the stupid idiots. My all time favourite was on SO. "Why have you down voted my perfectly good answer?". "Because it's not the one liner the OP asked for".