Where did you put track_changes? It is supposed to be in a model not in a module, certainly not in the module you are trying to reload.
On Friday, 2 August 2013 05:01:42 UTC-5, David Marko wrote: > > It has been reported a few times by different users. track_changes for > modules stops working after several reloads of page in browser. I can see > typical scenario ... I'm working with module and changes are detected > correctly . After 6-7 changes and reloads cycle in browser during the > coding process and testing web2py ... tracking stops detect the changes in > module. When for example I try to debug some error and web2py stops reload > the module I can see still the same source code snippet in error ticked > even though my module contains updated code. When this occurs (and this > occurs repeatedly for me /tested width rocket and mod_wsgi/) I observed > that .pyc file is outdated comparing the timestamp on original .py file. I > even tried to remove .pyc file but web2py(python) doesnt create a new one > when I reload the page in browser. I have to restart the web2py and things > get working for sometime once again. Any idea here please? -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
