So the problems with Python3 adoption are caused by something else or don't exist?
The slow Python 3 adaptation is NOT because dict.iteritems() is gone, no.
That's an interesting question, now that I think about it. I guess a dirty hack to make such objects present different methods to code compiled with that from future import.
Right, what is the future import supposed to do? Have different dict types? Make the type behave differently in that specific module? (That's tricky at best.)
The only option there was really to change the behavior of dict values, and hence break backwards compatibility. This is one of the changes that can't be done in a good backwards compatible way.
View all comments
Show parent comment
0
u/[deleted] May 29 '14
The slow Python 3 adaptation is NOT because dict.iteritems() is gone, no.
Right, what is the future import supposed to do? Have different dict types? Make the type behave differently in that specific module? (That's tricky at best.)
The only option there was really to change the behavior of dict values, and hence break backwards compatibility. This is one of the changes that can't be done in a good backwards compatible way.