Rationale for read-only property of co_code

João Neves sevenjp at gmail.com
Thu Apr 3 12:10:48 CEST 2008

On Apr 3, 4:43 am, Scott David Daniels <Scott.Dani... at Acm.Org> wrote:
> Nope:  If you change the code in-place, the whole stack's references
> to where they were running would need to get updated to corresponding
> locations in the new code.  _That_ is a lot of work.

Ah, there it is. Now I get it, it makes perfect sense.
Looks like I'll have to stick to the usual mechanisms!
Thanks everyone!

João Neves

More information about the Python-list mailing list