Re: Must a Django Database Support Migrations?

2014-01-21 Thread Shai Berger
Hi, (quotations reordered a little) On Wednesday 22 January 2014 14:48:25 Russell Keith-Magee wrote: > On Wed, Jan 22, 2014 at 1:51 PM, Michael Manfre wrote: > > *Why Disable Migrations?* > > > > 1) Not all projects need schema migrations or want Django to manage the > > migrations. My primary

Re: Must a Django Database Support Migrations?

2014-01-21 Thread Russell Keith-Magee
On Wed, Jan 22, 2014 at 1:51 PM, Michael Manfre wrote: > *Must a Django Database Support Migrations?* > > Django 1.7 adds schema migration support and this behavior is currently > required > to be able to effectively use Django and run the test suite. I opened > ticket > #21841 [1], which request

Must a Django Database Support Migrations?

2014-01-21 Thread Michael Manfre
*Must a Django Database Support Migrations?* Django 1.7 adds schema migration support and this behavior is currently required to be able to effectively use Django and run the test suite. I opened ticket #21841 [1], which requests adding a DatabaseFeature to disable schema migrations. This ticket p

Re: Enforce the use of a unicode string in settings.LANGUAGES

2014-01-21 Thread gilberto dos santos alves
please see that it is python directive not django. for all sources it is a good practive for all we that use pt-br utf-8 explicit this on second line of file python code # -*- coding: utf-8 -*- regards! 2014/1/21 Henrique Romano > Hi, > > As per the documentation[1], it is not clear that yo

Re: App-loading: Pragmatic concerns about default AppConfig objects and ready() implementations

2014-01-21 Thread Russell Keith-Magee
On Wed, Jan 22, 2014 at 2:03 AM, Carl Meyer wrote: > On 01/21/2014 06:48 AM, Russell Keith-Magee wrote: > > As Marc indicated in his post, I don't think we should be treating this > > as a permanent feature of the API, but as but as a migration aid. Yes, > > default_app_config will exist as a bad

Enforce the use of a unicode string in settings.LANGUAGES

2014-01-21 Thread Henrique Romano
Hi, As per the documentation[1], it is not clear that you _must_ use a unicode string for the language name. If you don't use an unicode string, the following can happen: >>> from django.utils.translation import ugettext >>> ugettext("Português") Traceback (most recent call last): ... UnicodeDec

Re: App-loading: Pragmatic concerns about default AppConfig objects and ready() implementations

2014-01-21 Thread Shai Berger
On Tuesday 21 January 2014 20:03:25 Carl Meyer wrote: > On 01/21/2014 06:48 AM, Russell Keith-Magee wrote: > > As Marc indicated in his post, I don't think we should be treating this > > as a permanent feature of the API, but as but as a migration aid. Yes, > > default_app_config will exist as a ba

Re: Ticket #21751 review requested

2014-01-21 Thread Michael Manfre
I agree with Aymeric in that cursors are very much like files. Wrapping a single line of code in a with (or a try-finally) is a standard pattern and allows Django to follow PEP 249 without extra modifications. The overall feedback I've gotten from my pull request seems positive. I'll rebase it aga

Re: App-loading: Pragmatic concerns about default AppConfig objects and ready() implementations

2014-01-21 Thread Carl Meyer
On 01/21/2014 06:48 AM, Russell Keith-Magee wrote: > As Marc indicated in his post, I don't think we should be treating this > as a permanent feature of the API, but as but as a migration aid. Yes, > default_app_config will exist as a bad smell for 2 releases, but come > Django 1.9, we can remove i

Re: App-loading: Pragmatic concerns about default AppConfig objects and ready() implementations

2014-01-21 Thread Russell Keith-Magee
On Mon, Jan 20, 2014 at 11:09 PM, Jannis Leidel wrote: > On 19.01.2014, at 08:56, Russell Keith-Magee > wrote: > > > Hi all, > > > > First off - this isn't critical for 1.7 alpha - I'm raising it now > because I've been in this space for the last couple of days as a result of > the working on th