Hi Ferran! In data lunedì 26 novembre 2012 16:41:02, Ferran Jorba ha scritto: > under the old mod_python Invenio, it was pretty easy to add minor local > web modules just placing them under the reach of Apache.
the old mod_python mod_publishing is still (almost) fully simulated and available even with 1.1 (we are using it also on production here at CERN :-) ). > Now, on my test 1.1 installation I'm errors like that: > > ** Traceback details > > Traceback (most recent call last): > File "/home/traces/lib/python/invenio/webinterface_handler_wsgi.py", line > 453, in application mp_legacy_publisher(req, possible_module, > possible_handler) > File "/home/traces/lib/python/invenio/webinterface_handler_wsgi.py", line > 598, in mp_legacy_publisher return _check_result(req, > module_globals[possible_handler](req, **form)) File "<string>", line 59, in > index > AttributeError: unreadable attribute I think there could be some bug in your handler, here. What pylint says about it? Isn't there anything in invenio.err/apache.err? > It is fine to me to leave mod_python back and learn to adapt my local > modules to wsgi, but even after inspecting webinterface_handler_wsgi I > don't know how to start, even with a trivial hello-world program. > > Where should I learn how to do it? Where, in 1.1 the old mod_python-like way is still the way to go, for plugging in new handler in your local installation. On the other hand in the next branch we are going for Flask! <http://flask.pocoo.org/> and in particular their concept of blueprint, to implement pluggable handlers: <http://flask.pocoo.org/docs/blueprints/> So I'd suggest you to have a look at the Flask documentation in order to get ready for the future :-) Meanwhile just use the old mod_python way, it should keep on working AFAIK. Cheers! Sam -- Samuele Kaplun Invenio Developer ** <http://invenio-software.org/>
