I had trouble using some member variables on my application object and
tracked it down to using autoreload in 0.3. I think the bug goes
something like this:
- In reload_mapping, the main module is reloaded with __import__. Due
to the usual pattern for writing web.py applications (app =
web.application(...)), a new application is created.
- By setting self.fvars = mod.__dict__, fvars gets objects from the
reloaded main module, which refer to the newly created application.
The user's URL-handling objects -- which are now in the OLD
application object's fvars -- refer to the NEW application object.
The effect is that the users' URL-handling objects see a "blank"
application that has lost any member-variable assignments and such.
Things like processors, not being subject to the bug, see the old
application object.
Does this seem like a reasonable diagnosis? If so, it may be the cause
of bug 204084 (although I haven't looked at the sessions code):
https://bugs.edge.launchpad.net/webpy/+bug/204084
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
