Open lambacck opened 13 years ago
I was holding off on including the monitor
module in the distribution until I was more convinced of its usefulness (in its current form, anyway). There are a number of ways to integrate the reloading behavior with an application (such as via a Stackless tasklet, for example), and I'm not sure how many of those I want to cover in this package.
It's true that it wouldn't hurt to cover the most common usages, however, so I'm definitely open to suggestions.
I was thinking that there could eventually be a couple of monitors. The current one could become the ThreadedMonitor.
I was looking at win32 change notification mechanisms. I know there are similar APIs for Linux. These could become AsyncMonitorWin32 and AsyncMonitorLinux (or if the Linux API actually applies to posix systems AsyncMonitorPosix) and maybe have an AsyncMonitor helper class that picks the right one.
I also just came across http://svn.python.org/projects/sandbox/trunk/xreload/xreload.py via http://posted-stuff.blogspot.com/2011/01/hands-up-who-has-customised-xreloadpy.html. I am wondering if it is worth integrating xreload support?
I added monitor to the modules list locally for install, but maybe the two files could be put into a package (pyreloader?). I am happy to provide a patch.