#13921: Inconsistent get_internal_type on official models' fields
---------------------------------------------------+------------------------
Reporter: mitar | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm going to mark this wontfix on the grounds that it is a bunch of code
shuffling that doesn't yield any particular benefit -- at least, the
ticket doesn't suggest any particular benefit.
Yes, there is a minor inconsistency. SlugField should probably just
reference the CharField type. But maintaining the inconsistency takes no
effort, and removing it will require a bunch of effort implementing a
deprecation timeline. Absent of a good reason to make this change, wontfix
seems like the best approach to me.
--
Ticket URL: <http://code.djangoproject.com/ticket/13921#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
