Wiadomość napisana przez Thomas Guettler w dniu 4 kwi 2012, o godz. 15:55:
> since most people have something like this in their code, a better solution > should require > only some additional characters. Thank you for your feedback. I disagree since it wouldn't address any of the original concerns from the proposal. Most importantly, reducing redundancy and creating a canonical place for storing information of a specific concept. > I think it is better if choices must be set explicit, not > implicit (auto-increment). As Dan Poirier pointed out, setting an explicit .id on a single Choice will let you do that. > Here is my solution, which is similar to way3 in your proposal. Doesn't support groups, uses the tuple-galore syntax, still leaves you with redundancy of having to first define available options and later building a choice dictionary. -- Best regards, Łukasz Langa Senior Systems Architecture Engineer IT Infrastructure Department Grupa Allegro Sp. z o.o. http://lukasz.langa.pl/ +48 791 080 144 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
