Dear Jay,
glad that it works now.
I got myself confused about terms such as language name and locale name.
Setting the locale via locale.setlocale does indeed have no influence on
the Django settings. I knew that but I misunderstood you. I set
locale.setlocale in the example because I wanted to make use of locale
details for correct currency display (i.e. the currency symbol, whether the
currency symbol is displayed in front of the numbers or after them, etc.).
I found than Django has some of the locale details implemented, e.g. the
thousand separator, but not all of them to my best knowledge.
To be honest: it is not really clear to me how Django distinguishes/defines
locale and language. For the definition of a locale, at least when looking
at locale.setlocale, the encoding is required additionally.
Best wishes,
Ulrich
Am Freitag, 19. September 2014 09:54:21 UTC+2 schrieb James Hargreaves:
>
> Thanks again for your reply Ulrich. I finally figured out the problem :)
>
> Towards the bottom of my settings.py I had mistakenly overwritten the
> LANGUAGE_CODE as follows:
>
> LANGUAGE_CODE = 'en'
>
> Django must determine the locale internally based on the LANGUAGE_CODE
> specified. Needless to say this line broke the locale lookup since *en*
> is not a valid language code.
>
> Once I removed the line above the locale was set correctly. In fact, I was
> able to remove the manual setlocale(...) call from my wsgi.py file without
> any issues.
>
> Thanks again for your help, it is very much appreciated :)
>
> Jay
>
> On 18 September 2014 22:08, James Hargreaves <james.ha...@gmail.com
> <javascript:>> wrote:
>
>> Hi Ulrich et al,
>>
>> Thanks again for your help.
>>
>> I'm having issues with your solution. It works when making a literal call
>> to locale but Django is not using the correct locale for some reason.
>>
>> I added this to my application.wsgi:
>>
>> import locale
>>
>> locale.setlocale(locale.LC_ALL, 'en_GB.utf-8')
>>
>> I added a context processor which outputs the following:
>>
>> def common(request=None):
>> return {
>> 'TODAY' : date.today(),
>> 'LOCALE' : locale.getlocale(),
>> 'LOCALE_DF' : locale.nl_langinfo(locale.D_FMT),
>> }
>>
>> And I added the following to my template:
>>
>> <pre>{{ LOCALE }}</pre>
>> <pre>{{ LOCALE_DF }}</pre>
>> <pre>{{ TODAY|date:"SHORT_DATE_FORMAT" }}</pre>
>>
>> Which unexpectedly outputs this:
>>
>> <pre>('en_GB', 'UTF-8')</pre>
>> <pre>%d/%m/%y</pre>
>> <pre>09/18/2014</pre>
>>
>> I also tried adding the locale.setlocale(...) line to my settings.py
>> instead but that had no effect either.
>>
>> Any ideas appreciated please.
>>
>> Thanks
>> Jay
>>
>> On 17 September 2014 07:38, James Hargreaves <james.ha...@gmail.com
>> <javascript:>> wrote:
>>
>>> Thanks Ulrich.
>>>
>>> No I think I've misread the documentation with regards it affecting the
>>> whole environment rather than the program.
>>>
>>> I'll try your solution myself but it looks like it will work, thanks!
>>>
>>> Jay
>>>
>>>
>>> On Tuesday, September 16, 2014, uvetter <rettev...@googlemail.com
>>> <javascript:>> wrote:
>>>
>>>> Dear Jay,
>>>>
>>>> I just tried to following in my wsgi.py file:
>>>>
>>>>
>>>> import os
>>>> import sys
>>>> import site
>>>> import locale
>>>>
>>>> site.addsitedir('/mypath/lib/python3.3/site-packages')
>>>>
>>>> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "test.settings")
>>>>
>>>> os.environ['HTTPS'] = "on"
>>>>
>>>> sys.path.append('/mypath/test')
>>>> sys.path.append('/mypath/test/test')
>>>> sys.path.append('/mypath/test/app1')
>>>> sys.path.append('/mypath/test/app2')
>>>>
>>>> activate_env=os.path.expanduser("/mypath/bin/activate_this.py")
>>>> exec(open(activate_env).read())
>>>>
>>>> locale.setlocale(locale.LC_ALL, 'en_US.utf-8')
>>>>
>>>> from django.core.wsgi import get_wsgi_application
>>>> application = get_wsgi_application()
>>>>
>>>>
>>>>
>>>> This sets the locale correctly for all calls to my Django application.
>>>>
>>>> I just realized that in your first post you mentioned that "this
>>>> affects the entire environment". I just read through the locale module
>>>> documentation, which states that "The C standard defines the locale as a
>>>> program-wide property ....". This means that there will be no system-wide
>>>> changes when you call locale.setenv(). Or did I misunderstand you?
>>>>
>>>> Best wishes,
>>>> Ulrich
>>>>
>>>> Am Dienstag, 16. September 2014 22:39:08 UTC+2 schrieb James Hargreaves:
>>>>>
>>>>> Thanks for your reply Ulrich.
>>>>>
>>>>> If I set the locale in WSGI would that persist for all connections? If
>>>>> so that sounds like the best option.
>>>>>
>>>>> Thanks
>>>>> Jay
>>>>>
>>>>> On Tuesday, September 16, 2014, <rettev...@googlemail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>> I ran into a similar problem yesterday while programming a web shop
>>>>>> with Django (Version 1.6, Python version 3.3) where language switching
>>>>>> should immediately have an effect on the way prices, etc. are displayed
>>>>>> (doing so by a <form action="/i18n/setlang/" method="POST" > in the
>>>>>> template and redirecting back to the page where it was called). The
>>>>>> locale
>>>>>> is indeed not set this way and needs to be set explicitly. What I
>>>>>> finally
>>>>>> came up with as a first working solution as part of a function:
>>>>>>
>>>>>> def convert_my_price(_price) # _price is a decimal.Decimal
>>>>>> language = django.utils.translation.get_language()
>>>>>> if language == 'en':
>>>>>> locale.setlocale(locale.LC_ALL, 'en_US.utf-8') #
>>>>>> 'en_GB.utf-8' didn't work for me
>>>>>> else:
>>>>>> locale.setlocale(locale.LC_ALL, 'de_DE.utf-8') # this is
>>>>>> the fallback
>>>>>>
>>>>>> _loc = locale.localeconv()
>>>>>> .
>>>>>> . # process the Decimal
>>>>>> .
>>>>>> return my_price_as_a_string
>>>>>>
>>>>>> After doing so I have access to the locale details stored in the
>>>>>> dictionairy _loc, like e.g. _loc['thousands_sep'],
>>>>>> _loc['currency_symbol']
>>>>>> in this function, but also everywhere else via locale.localeconv()
>>>>>> This function however is currently called from within class based
>>>>>> views, but also implemented as a template filter. Of course one should
>>>>>> not
>>>>>> set the locale every time when calling this function, as you mentioned
>>>>>> locale.getlocale() will should whether it was correctly set or not.
>>>>>>
>>>>>> Where you call locale.setlocale depends on your application. When you
>>>>>> only have to set it once maybe the best would be to call it in even in
>>>>>> e.g.
>>>>>> wsgi.py
>>>>>>
>>>>>> Best regards,
>>>>>> Ulrich
>>>>>>
>>>>>> --
>>>>>
>>>>>
>>>>> --
>>>>> a: 1 Oak Cottage, Town Lane, Mobberley, WA16 7HJ
>>>>> t: 01565 873 019 | 07899 872 306
>>>>> e: ja...@hargreaves.me.uk
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Django users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/django-users/9kuQBMknp9g/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> django-users+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to django-users@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/django-users.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/django-users/ca7c49a3-c3bc-4aa7-9234-6d3896c3e171%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/django-users/ca7c49a3-c3bc-4aa7-9234-6d3896c3e171%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> a: 1 Oak Cottage, Town Lane, Mobberley, WA16 7HJ
>>> t: 01565 873 019 | 07899 872 306
>>> e: ja...@hargreaves.me.uk <javascript:>
>>>
>>>
>>
>>
>> --
>> a: 1 Oak Cottage, Town Lane, Mobberley, WA16 7HJ
>> t: 01565 873 019 | 07899 872 306
>> e: ja...@hargreaves.me.uk <javascript:>
>>
>
>
>
> --
> a: 1 Oak Cottage, Town Lane, Mobberley, WA16 7HJ
> t: 01565 873 019 | 07899 872 306
> e: ja...@hargreaves.me.uk <javascript:>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/41e7a13c-239f-4634-bd0e-738170f45bcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
