Well, Python 3.0 was released a few days ago. I admit, I really haven't been keeping up much with Python development. Up until yesterday, Python 2.5 was all that I've used.
Anyway, I was curious. I was curious about all the backwards-incompatible changes to the language/libraries. I was curious about how WSGI dealt with Python 3.0. With the list of proposed WSGI 1.0 amendments for Python 3.0 (and the Web-SIG posts it referenced), I attempted to port both flup and ajp-wsgi.
It was interesting, at least, to see the issues in two different lights. Though flup and ajp-wsgi do the same thing conceptually, flup is pure-Python and ajp-wsgi is pure-C. The most pain for both, unsurprisingly, came from the new str/bytes distinction. While it was an annoying issue to deal with (and I realize as far as the spec is concerned, all details about it still haven't been worked out), I do welcome the change.
I've published both repositories, for the curious. They work for simple "Hello World" type applications. I kind of doubt that any frameworks have been ported to Python 3.0 yet. I probably won't touch them again until the spec has been clarified more. (Encoding of environ key/values? file_wrapper support with e.g. text-mode files?)
Interestingly, I didn't actually test the FastCGI and SCGI adapters with "real" web servers. (I don't have anything set up.) I used the flup client implementations to cross-test clients/servers on 2.x/3.0. So those flup WSGI servers might actually be broken.
Just so you know, I'm working on a native Python 3 framework (yet to see the public eye). I've tested it with your FCGI adapter and have had success with both Apache on Linux (via pipes) and LightTPd on Windows (via FastCGI server).
I don't have file upload support in yet and there is a bit of wonkiness in cgi.FieldStorage.
I tried to build ajp-wsgi-py3 but it fails with Python 3.2 because the C API was deprecated in 3.1 and removed on favour of capsules. I would have logged it as a bug, but trac wont let me log in with trac/trac1234......
I looked at it to see if i could fix it, but i cant work out the python c api, and cant find any good docs on it, or the changes needed to switch to capsules. sorry, or i would have sent a patch.
I am messing with this, because its kind of needed for using cherrypy with apache or lighttpd which now supports Python 3.2