On Sat, Mar 21, 2009 at 7:05 PM, Graham Dumpleton <[email protected]> wrote: > 2009/3/22 Florian Bösch <[email protected]>: >> On Mar 21, 7:25 pm, Clodoaldo Pinto Neto <[email protected]> >> wrote: >>> You don't need to act like a jerk to get attention here. Graham is
I'm having trouble keeping up with this thread because I fail to see why "touch <your wsgi file>" isn't the optimal solution? You could type that hundreds of times in the time its taken everyone involved to read & reply to this thread. :-) IMHO you should develop using the auto-reloading capabilities builtin to frameworks like Django and CherryPy, and *test* on setups *identical* to your production server (eg using mod_wsgi). At no point is repeated restarting of mod_wsgi via your project required. Hell, just map ":!touch <your wsgi file>" to some shortcut key in vim and get on with your life if you insist on using modwsgi for development! :-) Graham has lots of neat features lined up for 3.0. I'd like him to be able to focus on those and not the shortcomings of your particular workflow. ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
