On Aug 12, 7:41 am, Graham Dumpleton <[email protected]> wrote: > I believe I have finally fixed the UTF8/UCS2 issue for WSGI script > paths on Window, so am close to a final release candidate. This issue > was where unicode characters could be used in file system directories > holding WSGI script file, or in name of WSGI script file itself. > > The only remaining thing I am looking at is the UTF8/UCS2 issue as it > relates to WSGIPy3kWarningFlag and WSGIPythonHome directives on > Windows. Once I get my head around and do any further changes, will > create a tar ball for another release candidate. > > For the adventurous out there who are using the subversion trunk, > please consider an update and provide feedback if any problems seen. > Pay particular attention to whether logging via sys.stdout, sys.stderr > and wsgi.errors is working correctly, as had to make some tweaks to > that code. > > Let the countdown for gert screaming about problems begin. ;-) >
I did not test it yet, But I am defenatly going to scream if think WSGIPy3kWarningFlag is what I think it is.... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
