#36328: Deserialization of RangeFields not interpreting the range bounds into
Python types
-------------------------------------+-------------------------------------
Reporter: Sebastian Albert | Owner: (none)
Type: Bug | Status: closed
Component: contrib.postgres | Version: 5.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
range,serialization,postgres | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* easy: 1 => 0
* resolution: => needsinfo
* status: new => closed
Comment:
Hello Sebastian, thank you for taking the time to create this report. In
order to continue this ticket triage, we would need a way to reproduce the
issue using Django without requiring any other dependency. Ideally, could
you provide a test case for the Django codebase showcasing the issue and
the expected outcome? Or, a minimal Django test project and detailed
instructions to reproduce would also help.
Please feel free to reopen when a reproducer is provided for us to
continue the triaging process. Cheers!
--
Ticket URL: <https://code.djangoproject.com/ticket/36328#comment:1>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019635a974bd-14522d20-bab5-4945-8636-0baf405b8c21-000000%40eu-central-1.amazonses.com.
