[modwsgi] Re: mod_wsgi and custom encodings

2010-05-26 Thread Stephen Hansen
On May 25, 9:18 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: The list of encodings is calculated when Python is initialised. This is only partially true. The initial list is indeed calculated, but then you can register new encodings at any point you would like later. That's what I'm

Re: [modwsgi] Re: mod_wsgi and custom encodings

2010-05-26 Thread Graham Dumpleton
On 27 May 2010 05:33, Stephen Hansen apt.shan...@gmail.com wrote: On May 25, 9:18 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: The list of encodings is calculated when Python is initialised. This is only partially true. The initial list is indeed calculated, but then you can

[modwsgi] Re: mod_wsgi and custom encodings

2010-05-26 Thread Stephen Hansen
On May 26, 4:14 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: It wasn't stated clearly in your post that you were explicitly registering the codec. If you are indeed registering the codec explicitly, then that potentially gets around the Python initialisation needing to be associated

Re: [modwsgi] Re: mod_wsgi and custom encodings

2010-05-26 Thread Graham Dumpleton
On 27 May 2010 11:18, Stephen Hansen apt.shan...@gmail.com wrote: On May 26, 4:14 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: It wasn't stated clearly in your post that you were explicitly registering the codec. If you are indeed registering the codec explicitly, then that

Re: [modwsgi] Re: mod_wsgi and custom encodings

2010-05-25 Thread Graham Dumpleton
On 26 May 2010 02:33, Stephen Hansen apt.shan...@gmail.com wrote: On May 24, 8:12 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Where did you install the Python code file corresponding to the encoding? Does that file have access permissions such that the Apache service, which is