In development environment I suggest to use build-in webserver from wsgiref
module, see http://docs.python.org/2/library/wsgiref.html#examples
Then it's easy to run webserver in console and killstart it with Ctrl+C
keystroke. In production environment, use your prefered webserver like
On Thu, Dec 26, 2013 at 7:36 AM, Fredrik Bertilsson freb...@gmail.com wrote:
Also, it's not a python issue, it's an issue with your particular
stack. Other stacks do automatic reloading (for example, the web
server that Django uses).
Which web server do you suggest instead of Apache, which
On 12/26/13 12:57 AM, Fredrik Bertilsson wrote:
I am evaluating Python for web development and just found out that I need to
restart Apache after source changes on windows. Using linux the situation is
better but I still have to touch the wsgi file. Is it only me that finds this
being a major
I am evaluating Python for web development and just found out that I need to
restart Apache after source changes on windows. Using linux the situation is
better but I still have to touch the wsgi file. Is it only me that finds this
being a major drawback compared to PHP?
--
On Wed, Dec 25, 2013 at 09:57:42PM -0800, Fredrik Bertilsson wrote:
I am evaluating Python for web development and just found out that I need to
restart Apache after source changes on windows. Using linux the situation is
better but I still have to touch the wsgi file. Is it only me that
Also, it's not a python issue, it's an issue with your particular
stack. Other stacks do automatic reloading (for example, the web
server that Django uses).
Which web server do you suggest instead of Apache, which doesn't have this
problem? (I am not planning to use Django)
--
