#516501 RFH: libapache2-mod-python -- Python-embedding module for Apache 2

#516501#5
Date:
2009-02-21 22:03:38 UTC
From:
To:
Hello,
I'm hereby looking for a person to support DPMT[1] in maintaining
libapache2-mod-python. I did the latest team uploads, but I don't use it, so I'm
not the right person to maintain it.

[1] http://wiki.debian.org/Teams/PythonModulesTeam

The package has some bugs to triage, fix or else report upstream, other than
that it's not in a bad shape, but having someone that can cope with the package
in a good way is really needed.

A strict requirement is that the package needs to remain in the DPMT repository,
in reply we can offer sponsorship (I know the package so you can contact me for
any support/question) and mentoring.

Robert (the current co-maintainer) agreed to this RFH.


The package description is:
 The mod_python module supports web applications written in Python.
 Because the parser is embedded in the server as an Apache module, it
 will run much faster than traditional CGI.
 .
 This package is built for the current Python version.

#516501#10
Date:
2009-03-01 13:40:08 UTC
From:
To:
Sandro Tosi wrote:

As there is mod-wsgi, I doubt upstream will work on mod-python anymore.
Also I'd suggest that we remove mod-python from the archive if nobody is going
to step up and maintain it.

Cheers,

Bernd

#516501#15
Date:
2012-03-09 16:15:09 UTC
From:
To:
libapache2-mod-python (I've just finished switching all applications I
had to mod_wsgi) but I'm willing to put some effort into getting the
package in reasonable shape.

What I want to do:
- switch to dh_python2 (from python-central) (will probably commit that
  later today)
- switch to source format 3.0 (quilt) since dpatch is deprecated
- try to switch to dh sequencer
- fix lintian errors and warnings
- check Standards-Version (Ubuntu upgraded to 3.9.2)
- perhaps address some bugs of find patches that need to be applied
  (Launchpad contains a useful-looking patch, upstream SVN contains a
  few changes since 3.3.1)
- other misc packaging cleanups

Any objections, thoughts? Does anyone have a good reason to push hard
for removal instead?

Thanks,