#29598: contrib.postgres.FloatRangeField should be renamed DecimalRangeField
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Stefano
| Chiodino
Type: Bug | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"6de7f9ec60fbdc59797bc21803f16260bd203f04" 6de7f9e]:
{{{
#!CommitTicketReference repository=""
revision="6de7f9ec60fbdc59797bc21803f16260bd203f04"
Fixed #29598 -- Deprecated FloatRangeField in favor of DecimalRangeField.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29598#comment:11>
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/067.77c7bfcd0ab116be75310c9a4bbd2ac2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.