[ http://issues.apache.org/jira/browse/MODPYTHON-55?page=all ]
Jim Gallacher updated MODPYTHON-55:
-----------------------------------
Attachment: serverobject.c-jg20050531-1.diff
On further consideration, lets bypass the whole config issue and add a method
to serverobject.c:
static PyObject * server_get_mp_version(serverobject *self)
{
PyObject *version;
version = PyString_FromString(MPV_STRING);
if (!version)
return NULL;
Py_INCREF(version);
return version;
}
Usage: req.server.get_mp_version()
> Add a version attribute to the mod_python module.
> -------------------------------------------------
>
> Key: MODPYTHON-55
> URL: http://issues.apache.org/jira/browse/MODPYTHON-55
> Project: mod_python
> Type: Improvement
> Versions: 3.1.4
> Reporter: Nicolas Lehuen
> Assignee: Nicolas Lehuen
> Fix For: 3.2.0
> Attachments: serverobject.c-jg20050531-1.diff
>
> (asked by dharana) There is no easy way to know the version of mod_python
> used from within an handler. Why not try to add a version string attribute to
> the mod_python module ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
