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 can find something which is definitely significantly better than the status quo, which the majority of people would want to use, rather than just an alternative - something that we would be happy to be become the recommended default and present in the docs as such. Otherwise we just have 2 ways to do it.

I quite like Tom's suggestion here:


It's not perfect but seems a reasonable compromise given the constraints.


On 11/01/2019 14:55, Shai Berger wrote:
On Mon, 31 Dec 2018 23:40:53 +0000
Tom Forbes <t...@tomforb.es> wrote:
We currently have a -1 and a +1, does anyone else have any input on

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 comment.

Looks to me like at least a rough consensus of "eh, ok, if you really
want it..."

You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to