A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108114.html below:

[Python-Dev] What's L2R status?

[Python-Dev] What's L2R status? [Python-Dev] What's L2R status?skip at pobox.com skip at pobox.com
Sat Feb 19 19:08:38 CET 2011
    INADA> Sorry. There is a issue already.
    INADA> http://bugs.python.org/issue11205

>From Raymond's last comment on the above ticket:

> How much to change and how far to backport may make for a good python-dev
> discussion.

I think the simple patch I posted for 2.7 is probably all that should be
done for the 2.x series.  Briefly, change the visit order to evaluate the
key before the value, then use ROT_TWO to reorder the top of the stack for
STORE_MAP.

> I don't have any feelings about it one way or the other, but it would
> great to see Py3.2.1 get fixed properly.

I don't know if bumping the bytecode version is okay after 3.2 is released,
or if that's something which could only happen with 3.3.  Whatever is deemed
proper by the release managers, the better change would be to bump the
version number, remove the ROT_TWO from my basic patch and change the order
of arguments expected by STORE_MAP.

Skip
More information about the Python-Dev mailing list

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