It's definitely odd behavior. Do you see anything in your satchmo log file that might point us in the right direction?
-Chris On Fri, May 8, 2009 at 5:35 PM, bkev <[email protected]> wrote: > > Hi there... > > Yeah...I'm having the same issue still on Mac OS X (for months > now...had moved on to another project). My locale settings and > settings.py are identical to yours; ie: > > LANG="en_US.UTF-8" > LC_COLLATE="en_US.UTF-8" > LC_CTYPE="en_US.UTF-8" > LC_MESSAGES="en_US.UTF-8" > LC_MONETARY="en_US.UTF-8" > LC_NUMERIC="en_US.UTF-8" > LC_TIME="en_US.UTF-8" > LC_ALL= > > and settings.py > LANGUAGE_CODE = 'en_US' > > I'm currently on Satchmo SVN 2027 and Django SVN 10702, but this has > persisted for many, many versions - months back - at least since > Satchmo was reorganized. I don't hit this problem in Django > proper...just in Satchmo. I've experimented with quite a few > solutions, but to no avail. Don't quite know where to go from here... > (sorry, not much help). Anyone out there with a working OS X install > that cares to share their secret? > > -bkev > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
