Trying to recap all the discussion done in the mailing list, Trac and
Github:
The problem that was originally reported in #30439 was about mixed plural
forms in catalogs bundled with Django, which led to broken translations.
Then, it added the not announced changes in the plural forms of locales,
👍 ok, great. They're both good points. As to Adam's point about missing
warnings: it is true, they can be missed, but there are ways to enforce
them (python -W error, or PYTHONWARNINGS=error).
On Fri, Jan 10, 2020 at 12:41 PM Tim Graham wrote:
> I think issuing a warning would be rude to develop
I think issuing a warning would be rude to developers who want to use that
feature and are aware of the limitation... they would have to do extra work
to silence the warning.
On Friday, January 10, 2020 at 10:14:23 AM UTC-5, Santiago Basulto wrote:
>
> Sadly I have to admit that I'm not involved
Hi Santiago
There are any kinds of queries that can be slow in Django. ORDER BY
RANDOM() will be just as slow on large tables as ORDER BY
some_unindexed_column, or many other SQL constructs.
Django can't predict well how expensive a query will be - that's the job of
the database's optimizer. It v
Sadly I have to admit that I'm not involved with day to day development of
our app anymore (I miss it tremendously). Yesterday I felt nostalgic and
reviewed a few already-merged PRs, just "for fun" we could say. Great was
my surprise when I noticed that one of those PRs was merged with an
`orde
Am 08.01.20 um 22:39 schrieb Aymeric Augustin:
The original intent was to make configuration explicit by having
settings.py reference directly the target AppConfig class.
- When you write MIDDLEWARE = ["polls"], do you expect Django to
enable "polls.middleware.PollsMiddleware"?
- When you wri
