1276
Comment: What alternatives do you recommend to mod_python?
|
1277
converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
At [:PoundPythonWeb:#python.web] we warn against using mod_python. Here's a handful of the reasons: | At [[PoundPythonWeb|#python.web]] we warn against using mod_python. Here's a handful of the reasons: |
At #python.web we warn against using mod_python. Here's a handful of the reasons:
- It complicates your upgrade process, as versions of Python, Apache, and mod_python must be coordinated. The appropriate versions are not always available for some combinations.
- It makes user separation or chrooting of webapps impossible.
If you're using PHP and mod_python, and you're using MySQL in both languages, you generally must coordinate versions of MySQL as well, or suffer lots of configuration headaches. The same applies for many other popular C libraries.
- Apache's processes will be heavier because you're embedding a python interpreter in it.
- Debugging a wsgi app is a lot easier.
- mod_python is a module for Apache, which is tested less than other well known Apache modules such as mod_proxy. Because of this reason the server administrator (which might not be you) might not want to install this module for security reasons.
- You wont find a lot of hosting companies offering mod_python, which makes wsgi applications (which can be deployed through several ways) very flexible in your quest for a hosting company.
- Using nginx as a front-end is usually a more speedy and flexible solution.