Using UUIDField for id of custom User model prevents logging in

[James Beith]

When using the new UUIDField in Django 1.8 for the id of a custom User model, a session fails to be created and a TypeError exception is thrown when attempting to log in.

TypeError at /login/
UUID('314cb5d6-593f-48f5-b1af-fadedde123d3') is not JSON serializable

Please see the README.md file of the attached example project.

[James Beith]

Example project

[Simon Charette]

Thanks for the example project. Could you also provide the full traceback please.

[Simon Charette]

I guess we should use user.serializable_value(user._meta.pk.attname) ​here.

[James Beith]

Replying to charettes:

Thanks for the example project. Could you also provide the full traceback please.

​http://dpaste.com/3JNZ2YR

[Simon Charette]

Create a ​PR but I'm not sure get_prep_value is the correct solution here.

Maybe we should document that your session serializer should be able to deal with your user primary key type?

I guess we could also rely on the check framework to make sure it's the case.

[Simon Charette]

Tim's patch LGTM.

[Tim Graham <timograham@…>]

In 0f7f5bc9e7a94ab91c2b3db29ef7cf000eff593f:

Fixed #24161 -- Stored the user primary key as a serialized value in the session.

This allows using a UUIDField primary key along with the JSON session
serializer.

Thanks to Trac alias jamesbeith for the report and Simon Charette
for the initial patch.

[Tim Graham <timograham@…>]

In 596564e808089f1263469dbf4744dcaa05b79222:

[1.8.x] Fixed #24161 -- Stored the user primary key as a serialized value in the session.

This allows using a UUIDField primary key along with the JSON session
serializer.

Thanks to Trac alias jamesbeith for the report and Simon Charette
for the initial patch.

Backport of 0f7f5bc9e7a94ab91c2b3db29ef7cf000eff593f from master