I've significantly re-worked the patch to permit globals to be
arbitrary mappings.
The regression tests continue to all pass.
http://sourceforge.net/tracker/index.php?func=detailaid=1402289group_id=5470atid=305470
On 1/24/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Crutcher Dunnavant wrote:
. Löwis [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Aahz [EMAIL PROTECTED]; python-dev@python.org
Sent: Sunday, February 05, 2006 5:53 PM
Subject: Re: [Python-Dev] [PATCH] Fix dictionary subclass semantics whenused
as global dictionaries
I've significantly re-worked the patch to permit globals
Okay, but is there any reason not to include this in 2.5? There
doesn't seem to be any noticeable performance impact, and it does add
consistancy (and opens some really, really cool options up).
Does anyone have objections to 1402289?
On 1/12/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Crutcher Dunnavant wrote:
Okay, but is there any reason not to include this in 2.5? There
doesn't seem to be any noticeable performance impact, and it does add
consistancy (and opens some really, really cool options up).
I see no reason, except perhaps the lack of volunteers to actually
patch
Crutcher Dunnavant wrote:
I sorta disagree about it not being broken. Adding a feature which
works for eval but not for exec seems pretty broken.
You seem to have a different notion of to be broken, then.
Python is broken, if and only if
- the interpreter crashes, for any Python input
- the
Is there any objection to this patch? Any support?
It is assigned to me. When I have time, will go through it in detail
(the given use cases, more detailed timings, and a close reading of the
code).
If accepted, it will be for Py2.5, as it is a new feature. There is
nothing broken about the
I sorta disagree about it not being broken. Adding a feature which
works for eval but not for exec seems pretty broken. It's difficult to
reason about what will happen in the exec context, so I can't see what
fixing it would endanger; but I'd deffinately like to see it for 2.5.
I've run rough
