OpenID and Django
If you've ever gone to implement OpenID on your website, you'll know that it's not exactly an easy thing to do. Enabling OpenID is super easy to do if you're using Wordpress with wp-plugin. OpenID support is also built into Drupal. If you're not using those solutions, however, it's definitely not as simple as installing a module. It should be, however.
Simon Willison went a long way with his django-openidconsumer application, and extended a bit further with his basically unreleased django-openidauth which allows for a greater integration between an OpenID authenticated user and the contrib.auth system. Simon hasn't updated the module to use the openid2.0 libraries, which is very unfortunate - however, I was able to update it to use the 2.0 library in about 10 minutes while flying from Portland to San Francisco this morning.
But that's kind of the problem.
The resources are there, they just aren't really designed for easy adoption. Part of this I think is contrib.auth. It's designed to do authentication its way very well (namely, usernames are required, emails are not unique). It's easy to hack it so that you use emails to log in, but you're still using an improper model definition for that and there isn't really an elegant solution for using that. I'm not sure that piggy-backing OpenID onto contrib.auth is the best approach.
Regardless, I'm very interested in helping put together a good OpenID package for Django. I'll keep posting notes as I come up with them.