Re: Guidance regarding Django Deployment Process

same here, but i can help you with exp i have, (recently i deployed with nginx+uWSGI) let every one know if you get help from a better linux admin. you can contact me to get basic info which i aquired. On Friday, February 8, 2013 5:37:58 PM UTC+5:30, Kaung Htet Zaw wrote: > > Hi all, > > I am a

Re: Allowing Reverse, Single Inlines in Admin

Any new infos on this one? I'd love to see it in django. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To

Re: TIMEZONE default

Thank you Alex and Aymeric for your responses. Since that is the situation, maybe an explanation should be included in the settings documentation? On Saturday, February 9, 2013 5:51:51 PM UTC-5, Aymeric Augustin wrote: > > Alex' answer is correct — and "later on" is actually a few days ago :) >

Re: TIMEZONE default

Alex' answer is correct — and "later on" is actually a few days ago :) UTC isn't a best practice as much as a country-agnostic practice. You're supposed to put your own time zone there. There are a few other discrepancies between global_settings.py and the default project template, notably USE_

Re: TIMEZONE default

Hi Jonathan, I don't know the particular history of this setting, but this sounds like something that was done to maintain backwards compatibility. My guess is that when Django was first released, it defaulted to 'America/Chicago' but later on it was recognized that using UTC time on the server is

Re: Guidance regarding Django Deployment Process

Please ask questions about using Django on django-users. The topic of this list is the development of Django itself. Thanks, Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails fro

Re: Guidance regarding Django Deployment Process

Hey! I'm in a similar boat to you, but this mailing list is for the development of Django only, and not for general Django related questions. You might want to try asking on the django-users list. Luke On Fri, Feb 8, 2013 at 12:07 PM, Kaung Htet Zaw wrote: > Hi all, > > I am a teenager who h

TIMEZONE default

Hey everybody, Quick question. In version 1.6 why is TIME_ZONE in django.conf.global_settings set to 'America/Chicago', but in the default project template TIME_ZONE = 'UTC'? Shouldn't they be the same, and if so whic

Guidance regarding Django Deployment Process

Hi all, I am a teenager who have been picking up Django development in my own time. I have reached a state where I am relatively comfortable with the django framework, setting up a *local* development environment, dealing with database setup and installation of third-party packages etc. I have

Re: Next steps for ticket #18150

Added an updated patch last night. Could someone look it over? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.co

Re: Form validation - char field coerces *any* data into a unicode

On Saturday 09 February 2013, Yo-Yo Ma wrote: > A form that has a char field (e.g. "name") when provided a dict of data > will convert the value of "name" to a Unicode, no matter what. I understand > that this is desirable in some circumstances, but it can lead to things > > like: > >>> product.na

Re: Form validation - char field coerces *any* data into a unicode

I should note, the use case for this is when the data is being provided to the form through a mechanism other than normal HTTP form-encoded via request.POST, such as an API that consumes JSON. >>> product.name > u"{'haha': 'I am a dict'}" > > -- You received this message because you are subscr

Form validation - char field coerces *any* data into a unicode

A form that has a char field (e.g. "name") when provided a dict of data will convert the value of "name" to a Unicode, no matter what. I understand that this is desirable in some circumstances, but it can lead to things like: >>> product.name u"{'haha': 'I am a dict'}" Perhaps this is desirabl