Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<ol> <li><p>Depends on your website - if you only need static content, you can use static site generators (<a href="http://www.blogofile.com/" rel="nofollow">Blogofile</a>, <a href="http://ringce.com/hyde" rel="nofollow">Hyde</a> to name a few written in Python) or, if your website serves dynamic content, you should use some kind of framework (<a href="http://flask.pocoo.org/" rel="nofollow">Flask</a>, Django, etc). With static site generators all you need on the server is the webserver that serves your content, but with dynamic sites you might need extra libraries for various things like database support, caching, etc.</p></li> <li><p>The built-in webservers are usually meant for local development and are generally not suitable for production use. For latter use the specific apps like mod_wsgi (for Apache) or uwsgi (for Nginx) instead. But try to avoid mod_python!</p></li> <li><p>WSGI stands for Web Server Gateway Interface and is a standard protocol used between web server and web application (or framework). WSGI seems to be currently the only standard choice, so go with it.</p></li> </ol> <blockquote> <p>Also, according to this benchmark of python WSGI servers, gevent and mod_wsgi show great performance with low memory footprint. They don't claim themselves as web frameworks, what's the difference between them and the web frameworks like cherrypy, web2py.</p> </blockquote> <p>As said before, WSGI is just a way that web server talks with web application. CherryPy and web2py deal with templating, request and session handling and output this information via WSGI to the web server.</p> <p>And if you worry about the speed, then don't worry about it too much.. :)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload