On Aug 30, 5:15 am, Scott Hunter <shun...@nycap.rr.com> wrote: > Complaint #3: Having to do strange things (like double-imports and > reloads) to pick up run-time changes in my module. (This may be where > the complaint about 3rd party modules comes from.) > Response #3: I believe the issue here is that there is a module which > is being developed/debugged, but changes to it aren't getting picked- > up without re-starting the application (or doing "strange things"). > Were the module being developed located inside web2py during > development, then I believe edits would get picked up immediately.
Still the same if module in modules folder, but isn't this a general Python issue? If you don't want this then start developing in model & ony move to module once stabilised. F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
