Changes between Version 4 and Version 5 of TracModPython


Ignore:
Timestamp:
12/23/12 14:06:38 (23 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracModPython

    v4 v5  
    66These instructions are for Apache 2; if you are still using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7]. 
    77 
     8== A Word of Warning == 
     9 
     10As of 16^th^ June 2010, the mod_python project is officially dead.  If you are considering using mod_python for a new installation, '''please don't'''!  There are known issues which will not be fixed and there are now better alternatives.  Check out the main TracInstall pages for your target version for more information. 
     11 
    812== Simple configuration == 
    913 
     
    2125(Still on Debian) after you have installed mod_python, you must enable the modules in apache2 (equivalent of the above Load Module directive): 
    2226{{{ 
    23 a2enmod mod_python 
     27a2enmod python 
    2428}}} 
    2529On Fedora use, using yum: 
     
    3438   PythonInterpreter main_interpreter 
    3539   PythonHandler mod_python.testhandler 
     40   Order allow,deny 
     41   Allow from all 
    3642</Location> 
    3743}}} 
     
    4652   PythonOption TracEnv /var/trac/myproject 
    4753   PythonOption TracUriRoot /projects/myproject 
     54   Order allow,deny 
     55   Allow from all 
    4856</Location> 
    4957}}} 
     
    281289Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able download any CSS or images/icons. I used <Location /trac> `SetHandler None` </Location> to circumvent the problem, though I do not know if this is the most elegant solution. 
    282290 
     291=== Problem with zipped egg === 
     292 
     293It's possible that your version of mod_python will not import modules from zipped eggs. If you encounter an `ImportError: No module named trac` in your Apache logs but you think everything is where it should be, this might be your problem. Look in your site-packages directory; if the Trac module appears as a ''file'' rather than a ''directory'', then this might be your problem. To rectify, try installing Trac using the `--always-unzip` option, like this: 
     294 
     295{{{ 
     296easy_install --always-unzip Trac-0.12b1.zip 
     297}}} 
     298 
    283299=== Using .htaccess === 
    284300 
     
    367383 
    368384Note: For the above configuration to have any effect it must be put after the configuration of your project root location, i.e. {{{<Location /myproject />}}}. 
     385 
     386Also, setting `PythonOptimize On` seems to mess up the page headers and footers, in addition to hiding the documentation for macros and plugins (see #Trac8956). Considering how little effect the option has, it is probably a good idea to leave it `Off`. 
    369387 
    370388=== HTTPS issues === 
     
    391409 
    392410---- 
    393 See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe] 
     411See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [trac:TracNginxRecipe TracNginxRecipe]