I'll add a comment, but do you know of a better way to do it? The case is that you're running a separate long-running process: `paver watch_assets`
It has two threads, and you want to be able to kill the process cleanly. Without this (not so busy) wait, you would have to kill it with kill -9



> On Mar 31, 2014, at 13:36, David Baumgold <notifications@github.com> wrote:
> 
> In pavelib/assets.py:
> 
> > +    """
> > +    Watch for changes to asset files, and regenerate js/css
> > +    """
> > +    observer = Observer()
> > +
> > +    CoffeeScriptWatcher().register(observer)
> > +    SassWatcher().register(observer)
> > +    XModuleSassWatcher().register(observer)
> > +
> > +    print("Starting asset watcher...")
> > +    observer.start()
> > +    if not getattr(options, 'background', False):
> > +        import time
> > +        try:
> > +            while True:
> > +                time.sleep(2)
> But this is just busy-waiting -- it's not doing anything but sleeping. If that's really want you want here, can you at least add a comment to the code explaining why? Everything in me that cares about optimization and doing meaningful work is screaming out in horror, and I want to know why you are doing this.
> 
> —
> Reply to this email directly or view it on GitHub.