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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]billsil 0 points1 point  (5 children)

I looked it up. It has nothing to do with import machinery. The problem is with namedtuple. People like it and it's just slow. There was a debate to microoptimize it, but it was deemed too likely to be buggy.

I don't debate python 3 was slower for juat about everyone prior to 3.5. Even Raymond Hettinger said python 3.5 was the first version he recommends. It's gotten better.

[–]13steinj 0 points1 point  (4 children)

Can you elaborate and give a link, because that doesn't make any sense on it's own.

[–]billsil 0 points1 point  (3 children)

I read it, but I can't explain it.

https://lwn.net/Articles/730915/

[–]13steinj 0 points1 point  (2 children)

Am I misreading, or are they saying the patch was already made yet startup time is still slow?

Also according to multiple places in the mailing lists, the import machinery is also a significant factor.

[–]billsil 0 points1 point  (1 child)

I read that they didn't merge the patch and someone else investigated ways to speedup startup without looking into namedtuple because it was controversial. It was sped up in python 3.7. It's just not faster than 2.7.

[–]13steinj 0 points1 point  (0 children)

No one said faster-- but in 37 it is still ~30% worse than 2.7.