If you are going to get into the low level details of WSGI, the ensure you read PEP 3333 (not PEP 333).
http://www.python.org/dev/peps/pep-3333/ This has been updated for Python 3. Right now mod_wsgi isn't as strict as what PEP 3333 calls for and if you take a Python 2 WSGI hello world program as on site it will run when technically it isn't meant to. Well actually, if you using mod_wsgi 4.0 from source code repository it may not actually work as I have been slowly aligning it to PEP 3333 and so it may be more strict now. What you could do is skip that level and have a look at Bottle (http://bottlepy.org/docs/dev/) which claims Python3 compatibility, although not sure if it is strict to PEP 3333 or the less strict prior interpretation that mod_wsgi and some other servers were using before PEP 3333 finally came into being. Apart from the contents of the WSGI script/application needing to be different for Python 3, mod_wsgi configuration should be the same. Graham On 9 May 2011 15:00, Gnarlodious <[email protected]> wrote: > Thanks, wsgi is up and running I guess. Now to figure out how to run a > script... > > -- Gnarlie > http://Sectrum.com > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
