Christian Tismer wrote:
> Hi there!
>
> here has been this patch to the threadstate, which
> allows to override the tstate's frame access.
>
> I just saw the part of the patch that modifies
> pyexpat:
>
>
> f = PyFrame_New(
> tstate, /*back*/
> c, /*code*/
> ! PyEval_GetGlobals(), /*globals*/
> NULL /*locals*/
>
> where the PyEval_GetGLobals is used instead of
> tstate->frame->f_globals
>
> Well, this unfortunately is not sufficient
> for this module, since pyexpat still *has* direct
> access to tstate->frame, in a much worse way:
> pyexpat does read and write the frame variable!
Ah!!
Can it be that PyEval_GetFrame() is just indended
to signal to an extension like Psyco that it needs
to quickly invent a frame now?
So it is *not* thought of to be a complete interface
for accessing tstate->frame no longer explicitly,
is is only meant for read access?
So I can't move it elsewhere and probably need
to work around that forever, unless we also
write PyEval_SetFrame()
sigh - ciao - chris
--
Christian Tismer :^) <mailto:tismer@tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
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