Le vendredi 11 janvier 2019 07:46:04 UTC+1, Uri Even-Chen a écrit :
>
> https://code.djangoproject.com/ticket/10852
>
> I also don't like the "fuzzy" keyword and I spent hours in deleting them
> from our django.po files after running makemessages.
>
Hi Uri,
Create your own makemessages command
Regarding the "default keyword TODO": there are tools that can be used
for working with translations, in the gettext suite.
For instance, for a given django.po file, the following command prints
all untranslated strings:
msgattrib --untranslated path/to/django.po
We have the
I've also tried to come up with something better than Django's current
default, using Enums, and found them lacking when it comes to the
caption, especially when you need translations.
I would be happy with re-opening the ticket, but in terms of committing
a solution I would be -1 unless we
On Mon, 31 Dec 2018 23:40:53 +
Tom Forbes wrote:
>
> We currently have a -1 and a +1, does anyone else have any input on
> this?
>
So, the tally is +3, -1, and the -1 seems to be based on a technical
argument which I believe I refuted; and more than a week has passed
with no further
Shai, your rebuttal still misses an important use case, which is
containment.
To continue with your example of a 'SchoolYear(str, Enum)', the following
will both be False:
'FR' in SchoolYear
'FR' in SchoolYear.__members__
The first of those is also becoming illegal soon -- attempting an 'in'
> On 10 Jan 2019, at 20:16, Adam Johnson wrote:
>
> It will be hard for any new fellow to match you.
I go for “aspire to…”
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this
I am using ``APPEND_SLASH = True`` (the default) and usually use a
trailing slash in all of my URL patterns.
This works great for the most part, but some API clients send
POST-requests without the slash and then change the request method to
GET on the subsequent request. In particular, a popular
I completely agree.
Even without getting into API clients, the intent of this option is to tell
everyone that the canonical URL is not that, not disrupt normal operations.
The same can be said about the http->https redirect. There's no security
problem here, as the data has already been sent in
