On Fri, Dec 5, 2008 at 6:07 PM, dayvo <[EMAIL PROTECTED]> wrote: > > Good question. That could affect the app if I were using relative > path's or relying on the environment to locate files. The path's I'm > using in the app are stored are absolute paths. They work correctly > for path's that don't have unicode characters in them. My Django app > works correctly with %95+ of the data I'm using. I'm just trying to > resolve exceptions. Those exceptions all have special characters in > them. > > I'm starting to suspect apache and mod_python could have something to > do with this. Perhaps it's not a Django issue after all. >
Part of the locale is the preferred encoding, and I believe that will impact how unicode objects are encoded to bytestrings for system calls regardless of whether you are dealing with absolute or relative paths. Import locale in your test and check the value returned for locale.getpreferredencoding(). It appears when running under the shell your preferred encoding is utf-8 while when running under your server (Apache?) it is ascii. See http://code.djangoproject.com/ticket/8965 for an example of this sort of thing happening when running under Apache. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
