--
Ticket URL: <https://code.djangoproject.com/ticket/33720>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
> Changing `django_blog` to `theme_blog` to match the class name
> `ThemeBlog` will make the example clearer to read.
>
> https://github.com/django/django/blob/19297de2fe5a9c47e471c64249366f39fe12f16a/docs/topics/db/queries.txt#L1378
New description:
Changing `django_blog` to `theme_blog` to match the class name `ThemeBlog`
will make the example clearer to read.
8 occurrences of the term
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33720#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
In this example we create a theme blog called `Django`, so `django_blog`
sound appropriate to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/33720#comment:2>
* resolution: wontfix => invalid
--
Ticket URL: <https://code.djangoproject.com/ticket/33720#comment:3>
Comment (by Vlada Macek):
Respectfully I disagree.
But of course refrain from pushing it further. :-)
I didn't even notice the name value. The class name is IMHO more important
to indicate to the new developers.
I raised the ticket, because the inheritance sub-issue discussed in the
paragraph was by itself pretty nontrivial for me to comprehend. :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/33720#comment:4>