I agree with the removal, it wasn't providing much value and was making it unclear as to what it actually aws. It could easily be mistaken by a beginner for a performant alternative to M2M models or something like django.contrib.postgres' ArrayField. Additionally it was weird that Django would offer a single model field that's just differs from another by a single validator function - why not offer CommaSeparatedStringField, OddIntegerField, etc. ?
On 15 May 2017 at 18:21, Tim Graham <timogra...@gmail.com> wrote: > The CharField(validators=[validate_comma_separated_integer_list]) version > is more explicit about how the database stores the data. In my mind, having > a separate field could give the impression that the database uses a special > field type or validation. Also, I think > CommaSeparatedIntegerField is/was generally something to avoid -- I've > never seen it used myself. > > On Monday, May 15, 2017 at 12:57:59 PM UTC-4, Donald Morrone wrote: >> >> I see that CommaSeparatedIntegerField is being deprecated, but I don't >> see why. I know I'm apparently late to the discussion, but after it 16 >> months I don't see any actual reasoning. >> >> I recognize that a CharField with the validator is functionally >> equivalent, but it takes a very handy field type and makes it completely >> inaccessible and invisible to new users. >> >> I see this discussion: https://groups.google.com/forum/#!topic/django- >> developers/wfp9qNpNpaQ/discussion which lead to this ticket: >> https://code.djangoproject.com/ticket/26154 >> >> Both links focus on the *how* rather than the *why*. >> >> I disagree with the decision overall, but I'm more concerned that it just >> kind of slipped through without anyone really thinking about it. >> >> (To be clear, I don't begrudge Tim Graham, he was right to propose it, >> but then there was no discussion on it at all that I saw) >> > -- > 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 https://groups.google.com/d/ > msgid/django-developers/6e661a98-df55-4be5-852e- > 99788df05945%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/6e661a98-df55-4be5-852e-99788df05945%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adam -- 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 https://groups.google.com/d/msgid/django-developers/CAMyDDM2F5rvBRUhm0k8NEGp8a%3DD%2B5WPtM%3DgV2%3DRz3mK_1rZXdQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
