Re: Spyce application config file issue
"Jonathan Ellis" <[email protected]>
| Newsgroups | gmane.comp.python.spyce.general |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 25 Feb 2006 16:47:01 -0500, "Bruce Webber" <[email protected]> said: > --Jonathan Ellis <[email protected]> wrote: > > > This is a fundamental effect of the mod_python architecture. That is, > > since mod_python creates a certain number of long-running Python > > processes, the normal Python behavior is exhibited that for each "import > > foo" statement, foo.py is located once and its location cached for > > subsequent imports. > > > > Your options include, in order of increasing difficulty, > > > > 1) use the built-in Spyce server for development instead of apache + > > mod_python > > Thanks, Jonathan. > > So I could run apache + mod_python (port 80) for production, along with > the > built in Spyce server (port 8000) for development on the same server? > This > would be perfect. That should work just fine. -Jonathan -- C++ is history repeated as tragedy. Java is history repeated as farce. --Scott McKay ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642