On 3 Oct 2016, at 16:39, django-developers@googlegroups.com wrote:
=
Today's topic summary
=
Group: django-developers@googlegroups.com
Url:
See discussion here: https://code.djangoproject.com/ticket/21794
To summarise, when an abstract model class has no app_label, Django
currently says:
RemovedInDjango19Warning: Model class [model] doesn't declare an
explicit app_label and either isn't in an application in INSTALLED_APPS or
Done.
On 10 Sep 2014, at 10:45, Andrew Godwin wrote:
Looks good - make a pull request and I'll hit merge.
On Tue, Sep 9, 2014 at 3:05 PM, Greg Brown <gregplaysgui...@gmail.com>
wrote:
How's this?
https://github.com/gregplaysguitar/django/commit/b4d486c80ff6bdfaec8f85e724b44ce5e7
How's this?
https://github.com/gregplaysguitar/django/commit/b4d486c80ff6bdfaec8f85e724b44ce5e74a5bb6
On Wednesday, 10 September 2014 09:42:52 UTC+12, Greg Brown wrote:
>
> Hi all,
>
> Thanks for the rapid responses! I wasn't aware that South imported the
> custom fields, and I
afresh now.
>
> Andrew
>
> On Tue, Sep 9, 2014 at 2:27 PM, Carl Meyer <ca...@oddbird.net
> > wrote:
>
>> Hi Greg,
>>
>> On 09/09/2014 03:00 PM, Greg Brown wrote:
>> > Moving over to the new migrations, I noticed that whenever I
>> > crea
Hi all,
Moving over to the new migrations, I noticed that whenever I
create a migration involving a custom model field, it imports that field
at the top of the migration. The South docs were always quite firm about
not doing this sort of thing, in case the code changed in the future. Is
this a
