last_login should reflect real activity

[Alper Cugun]

It looks like User.last_login is only triggered on a real login action. This does not in any way reflect real activity on a site if somebody saves their session.

Request: last_active field which is updated on a much more granular level on each request or such.

[Honza Král]

This is out of scope for django. It would be a backwards incompatible change and could cause problems with high traffic sites. Since there is nothing stopping you from tracking last user activity by some other means I am marking this as wontfix.

[Matthew Schinckel]

As a tip: you could use a middleware to do this, very easily.