Heh, I just made this info.wsgi up yesterday:
def application(env, respond):
respond('200 OK', [('Content-Type', 'text/plain')])
for k, v in sorted(env.iteritems()):
yield '%s: %r\n' % (k, v)
I've wanted this before, and since I always used to keep an info.php
lying around, as
2008/9/23 Brian Smith [EMAIL PROTECTED]:
Graham Dumpleton wrote:
2008/9/20 Carl Nobile [EMAIL PROTECTED]:
If this existed, you would still need to have a WSGI script
file that invokes it. The problem though is that core
mod_wsgi is C code only and want to keep it that way. Ie.,
don't want
2008/9/20 Carl Nobile [EMAIL PROTECTED]:
mod_wsgi is not a framework, so don't expect it to generate web pages for
you it is a way of using WSGI (Web Service Gateway Interface) with apache
only, and is very light weight compared to other alternatives. You could get
what you want from
Graham, I like your approach to this it will keep things very decoupled and
would still allow a developer to generate stats on what is going on inside
mod_wsgi. It would be cool to start seeing its use in something like Djangos
admin. The assumption here is that you would provide a Python API into
