#20546: New model – ApproximateDateField
-------------------------------------+-------------------------------------
Reporter: vericule@… | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by lukeplant):
There is no reason why this feature needs to live in Django core, and at
the moment I don't think there is a big demand for it.
If there is already a 3rd party solution, use that. If it is not
maintained, and there is only one, that is evidence there isn't a huge
amount of demand for this feature. Accepting this feature request will not
magically create some people willing to write and maintain this code, so
I'm going to have to WONTFIX, sorry.
Please bring this up on the DevelopersMailingList if you want to persuade
us that there is big demand for this feature and it needs to be in Django
itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/20546#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/078.409322e1e835be44cad472d5e9f82ac0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
