> >>It mentions that code like that
> >>
> >> {f1():f2(), f3():f4()}
> >>
> >>Will call these functions in the order f2, f1, f4, f3. What should we
> >>do about it? Tim mentions that "When [Tim] asked Guido about that
> >>some years ago, he agreed it was a bug.". Is it too late to fix it, or
> >>is it still a desirable fix?
>
> [Guido van Rossum]
>
> > ...
> > What does Jython do?
>
> Jython happens to evaluate in order of f1, f2, f3, f4. An accident, I'm
> sure, of the way the dictionary constructor is called with a sequence of
> (key, value, key, value, ...).
In that case, I see no reason to block the fix for this particular
case.
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4