Request to include fixes to UUID field onto the 1.8.x branch

[James Rivett-Carnac]

There is a problem in 1.8.3 where DjangoJSONEncoder cannot handle UUIDs.  This impacts several other projects, django-allauth and grapelli to name a couple.  While this has been fixed  https://code.djangoproject.com/ticket/25019 DjangoJSONEncoder does not encode UUIDs, this was marked as new feature.  (I've commented on the ticket as well).

I'm loath to reopen the ticket, since it does what it says it does and has been merged into master.  However I'd like to see this code included into 1.8.4, as django is not currently behaving in an expected way with UUIDs (see ticket).

What would be the process of getting this done? should I reopen the ticket and recatagorize it?

-- J

[Russell Keith-Magee]

Hi James,

I'm inclined to agree - the fact that Django added a new field type in 1.8, but can't serialize that type should be considered a bug, not a new feature.

If there's no objection on this thread, then the ticket should be re-opened, and a pull request for the backport submitted.

Yours,

Russ Magee %-)

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fc4ea8b7-093f-4dca-b37e-54270bcdbc57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Rivett-Carnac]

I shall do so.