Hi Yoan,
However, the autoreloader works by exiting (SIGINT I think) the
process. Any web service process should have a controller process,
making sure it's alive (i.e. by running the process as a child in
apache or lighty), thus the app will be restarted (rather than
reloaded).
It it constructed like this because of the high level of complexity
where caches and things like that would otherwise be out of sync if we
only reload modules (using reload()). You are of course welcome to
create an autoreloader class which implements this, but keep in mind
the complexity of the task and the problems arising from not going the
whole way.
PS what is wsgi.util.main.Main doing? How about logging,
smisk.core.bind and setup_appdir? Are those covered?
(I also put this answer/comment onto the change set referenced earlier
[1][2])
[2]
http://github.com/greut/smisk/commit/8844d8db3754dac29cd1488b6a24424b4353cec1#comment_27184
> [1]
http://github.com/greut/smisk/commit/8844d8db3754dac29cd1488b6a24424b...