[IronPython] What's the situation on being able to accept patches?
dinov at microsoft.com
Thu Oct 16 08:42:00 PDT 2008
This is because we're not firing the module changed event. This seems like a bug, we should probably use a special dictionary here. You can call ScopeOps.SetMember() and it'll also deliver the event.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dan Eloff
Sent: Wednesday, October 15, 2008 9:46 PM
To: Discussion of IronPython
Subject: Re: [IronPython] What's the situation on being able to accept patches?
I figured it out. It seems that depending on where the compile calls
are located, they might call the old or the new compile function.
compile(...) # old compile
__builtins__.compile(...) # new compile
I'm looking into how to get the new compile without messing up mako's
code any more than absolutely required.
Thanks for the code. It works, and I never would have figured it out
without your help.
On Wed, Oct 15, 2008 at 10:10 PM, Dan Eloff <dan.eloff at gmail.com> wrote:
> Ok, I made the changes, PerformModuleReload is called, SetName is
> called, but only the builtin compile is called, the one on
> CompileHelper is never called. Any idea why? Here's my code:
Users mailing list
Users at lists.ironpython.com
More information about the Users