#29147: Postgres JSONField missing to_python
-------------------------------------+-------------------------------------
Reporter: Javier Buzzi | Owner: Williams
| Mendez
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
In your patch, I think you missed the `JSONField.value_to_string()` that's
already defined. It overrides the one you added since it's declared below
yours. The test failure happens if you remove the existing
`value_to_string()` method in favor of yours. Anyway, if you provide a
pull request that passes all tests and includes a test for the new
behavior, I'll take a closer look to see if this is suitable.
--
Ticket URL: <https://code.djangoproject.com/ticket/29147#comment:12>
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/069.4027921a82fb6ad30575e87e25bc39fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
