On 19 janv. 2015, at 21:13, Andreas Kahnert <kahn...@cruise-systems.com> wrote: > I advertise that strongly against lists, because we actually had that kind of > issue in our company.
Hi Andreas, This is probably obvious, but I thought I’d mention it just in case — you can keep using tuples in your projects. We’re just talking about standardizing the docs and the default values. I understand your arguments and I can see how your experience led you there. However, like others, I believe that encouraging “almost immutable” values would provide a false sense of security and cannot be a substitute to an understanding of Python’s data model. By “almost immutable” I refer to the fact that even if settings.FOO is immutable you can still overwrite it, especially with += whose difference with append will be lost on someone who doesn’t understand the data model. -- Aymeric. -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6FB499CB-1772-4120-9A3D-06EFA14AB1D5%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
