Model.__repr__() should include the pk

[Álex Córcoles]

This was proposed on https://code.djangoproject.com/ticket/1055 , but it was fixed without including the PK. It was also suggested in https://code.djangoproject.com/ticket/20448 , but ignored.

I think the PK is very valuable as __repr__, as it allows you to retrieve the object unambiguously; while str really can't have a good default implementation.

[Tim Graham]

This is effectively fixed (unless Model.__str__() is overridden) in Django 2.0 by #27953 which includes the pk in the default Model.__str__(). I'm not sure if further changes should be made.

There's some related discussion in #20448.

[Álex Córcoles]

Doh, sorry, I did not find #27953. Just tested it and it works perfectly, I'm closing this as a duplicate myself.

[Álex Córcoles]

Sorry again, after taking a look at the implementation, I disagree slightly; the PK should be included in repr, not str. It's nice to have a default repr implementation with the PK for use in the shell et al., but str is used for stuff such as choosing the displayed str on a dropdown- where I think a PK is out of place...

(You might close this again if you guys disagree- I'm OK with that, but I wanted to make my full case).

[Tim Graham]

The place to revisit the decision would be on the ​django-developers thread. Comments in this ticket tracker don't reach a wide audience.

[Álex Córcoles]

For completion sake: ​https://groups.google.com/d/msg/django-developers/7Jqzwg5nt-c/DqyXOBy3BQAJ