local_import should work, but you should now use regular import statements
instead. If you want your modules reloaded automatically, do the following:
from gluon.custom_import import track_changes
track_changes()
That will reload your modules, but only when they change (which is an
improvemen
Good to know that.
One thing though. If track_changes() is that good, how about we always
put it in every app's db.py? Any pros and cons?
Thanks in advance.
Regards,
Iceberg
On Jul 9, 3:20 am, Anthony wrote:
> local_import should work, but you should now use regular import statements
> instead
I have a 0.py file that is versioned for production and development (mainly
to use postgres on prod and sqlite in dev). I put track_changes() in my dev
file.
Fantastic, that is exactly what I was looking for!
-Jim
On 7/8/2011 2:20 PM, Anthony wrote:
local_import should work, but you should now use regular import
statements instead. If you want your modules reloaded automatically,
do the following:
from gluon.custom_import import track_changes
4 matches
Mail list logo
