#26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't round trip in serialization -------------------------------------+------------------------------------- Reporter: bukin242 | Owner: nobody Type: Bug | Status: closed Component: contrib.postgres | Version: 1.9 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: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>): In [changeset:"205cafd01ebe0f1c72ef3772a1b3f195387f4c50" 205cafd0]: {{{ #!CommitTicketReference repository="" revision="205cafd01ebe0f1c72ef3772a1b3f195387f4c50" [1.9.x] Fixed #26215 -- Fixed RangeField/ArrayField serialization with None values Also added tests for HStoreField and JSONField. Thanks Aleksey Bukin for the report and Tim Graham for the initial patch and the review. Backport of 928c12eb1 from master. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/26215#comment:10> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.7343d9e171224599b856ee75e9145775%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.