@Anthony- There's really nothing specific to post, its a general thing, and not the first time i've dealt with it- just that this code fix doesn't change anything. Moreover, now I'm experiencing some truly odd behavior.
1. I have a module that was throwing an error, and fixing it doesn't seem to update. 2. I quit python, restart web2py 3. The page loads fine, module working. 4. I make a change- ANY change, including change in comments- and i start getting error tickets again, as if the old broken version of the module is still cached somewhere- how this would persist after quiting and restarting web2py makes no sense to me. It's just too erratic to track down. I'm working locally with the rocket server on a Mac, if that means anything to anybody. On Saturday, April 28, 2012 9:43:42 AM UTC-4, Yarin wrote: > > For dev purposes, it would be nice to be able to reload modules without > having to restart the server- or to have a setting that automatically > reloads on each request- Otherwise it's almost impossible to do active > module development from within web2py.
