#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

 * status:  assigned => closed
 * resolution:   => invalid


Comment:

 I don't think that change is correct because
 
[https://github.com/django/django/blob/16436f3751e9eec67a7b80b25c8e7d29a34be67e/tests/postgres_tests/test_json.py#L46-L50
 a string is valid JSON] -- to treat it differently would break backwards
 compatibility.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29147#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 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.379de62ed35c9779535663fc33c276a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to