Comments on: Autoreload/Restart modwsgi on source change http://www.djangofoo.com/320/autoreloadrestart-modwsgi-on-source-change Django Tips and Tweaks Fri, 25 Mar 2011 12:22:36 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: sabueso http://www.djangofoo.com/320/autoreloadrestart-modwsgi-on-source-change/comment-page-1#comment-1081 sabueso Wed, 26 Jan 2011 20:34:01 +0000 http://www.djangofoo.com/?p=320#comment-1081 I wrote some easier code , but work great. http://blog.sabueso.org/40 I wrote some easier code , but work great.
http://blog.sabueso.org/40

]]> By: Graham Dumpleton http://www.djangofoo.com/320/autoreloadrestart-modwsgi-on-source-change/comment-page-1#comment-177 Graham Dumpleton Sun, 20 Jun 2010 12:31:08 +0000 http://www.djangofoo.com/?p=320#comment-177 The code already tracks the .py files, you don't need to call track() for them explicitly. It knows which .py files to monitor as it scans through sys.modules looking for what modules have actually been imported by the application and what the corresponding .py files for them may be that need to be checked. Check closely what the loop in the code over sys.modules.values() does. The code already tracks the .py files, you don’t need to call track() for them explicitly. It knows which .py files to monitor as it scans through sys.modules looking for what modules have actually been imported by the application and what the corresponding .py files for them may be that need to be checked. Check closely what the loop in the code over sys.modules.values() does.

]]> By: Davo http://www.djangofoo.com/320/autoreloadrestart-modwsgi-on-source-change/comment-page-1#comment-176 Davo Sun, 20 Jun 2010 12:24:21 +0000 http://www.djangofoo.com/?p=320#comment-176 Hello Graham, I updated the post so it links to modwsgi. I don't get what you mean by using it wrong and tracking on NON PYTHON code? I am using Django here and monitoring only the .py files isnt this the correct way of handling it ? OUT OF TOPIC: I still have the issue killing the processed spawned by modwsgi process, remember the ones which become parent when its restarted? :) Hello Graham,

I updated the post so it links to modwsgi.

I don’t get what you mean by using it wrong and tracking on NON PYTHON code?

I am using Django here and monitoring only the .py files isnt this the correct way of handling it ?

OUT OF TOPIC:
I still have the issue killing the processed spawned by modwsgi process, remember the ones which become parent when its restarted? :)

]]> By: Graham Dumpleton http://www.djangofoo.com/320/autoreloadrestart-modwsgi-on-source-change/comment-page-1#comment-175 Graham Dumpleton Sun, 20 Jun 2010 12:15:27 +0000 http://www.djangofoo.com/?p=320#comment-175 If you are going to take code out of some one else's documentation then at least link back to the original with an attribution. I cant see that you have done that. The original code is at 'http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode#Monitoring_For_Code_Changes'. Also be aware that you are using it wrongly anyway. You don't need to call track() for all files as the code will automatically track changes related to any loaded Python code files. You only need to call track on non Python code files which a Python framework might not itself auto detect changes in. In other words, most web frameworks detect changes automatically in page templates and will reload them internally. Thus pointless having this monitor code checking those. If you are going to take code out of some one else’s documentation then at least link back to the original with an attribution. I cant see that you have done that. The original code is at ‘http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode#Monitoring_For_Code_Changes’.

Also be aware that you are using it wrongly anyway. You don’t need to call track() for all files as the code will automatically track changes related to any loaded Python code files. You only need to call track on non Python code files which a Python framework might not itself auto detect changes in. In other words, most web frameworks detect changes automatically in page templates and will reload them internally. Thus pointless having this monitor code checking those.

]]>