Tim Peters [EMAIL PROTECTED] writes:
Rev 2.66 of funcobject.c made func.__name__ writable for the first
time. That's great, but the patch also introduced what I'm pretty
sure was an unintended incompatibility: after 2.66, func.__name__ was
no longer *readable* in restricted execution mode.
[Michael Hudson]
...
Well, I fixed it on reading the bug report and before getting to
python-dev mail :) Sorry if this duplicated your work, but hey, it was
only a two line change...
Na, the real work was tracking it down in the bowels of Zope's C-coded
security machinery -- we'll let you do
Tim Peters [EMAIL PROTECTED] writes:
[Michael Hudson]
...
Well, I fixed it on reading the bug report and before getting to
python-dev mail :) Sorry if this duplicated your work, but hey, it was
only a two line change...
Na, the real work was tracking it down in the bowels of Zope's C-coded
[sorry for the near-duplicate msgs -- looks like gmail lied when it claimed the
first msg was still in draft status]
Did you add a test to ensure this remains fixed?
[mwh]
Yup.
Bless you. Did you attach a contributor agreement and mark the test
as being contributed under said contributor
Tim Peters [EMAIL PROTECTED] writes:
[sorry for the near-duplicate msgs -- looks like gmail lied when it claimed
the
first msg was still in draft status]
Did you add a test to ensure this remains fixed?
[mwh]
Yup.
Bless you. Did you attach a contributor agreement and mark the test
Rev 2.66 of funcobject.c made func.__name__ writable for the first
time. That's great, but the patch also introduced what I'm pretty
sure was an unintended incompatibility: after 2.66, func.__name__ was
no longer *readable* in restricted execution mode. I can't think of a
good reason to
