My understanding is that this pull request is no longer necessary based on the commits that were made a couple of weeks ago. I've deployed trunk into production with Django 1.5 and everything is working very well! Updating your backends to use the new class based view system only takes about 20 minutes. What we really need is a new release pushed to pypi.
If you install this app while using a custom user model, Django gives you the "Manager isn't available; User has been swapped for 'app.UserModel' error, even before you syncdb. This is coming from the model itself, so I don't think we can subclass this problem away, unless I'm missing something. Subclassing the CBVs works brilliantly, and the whole thing is great once you edit model.py to use get_user_model...
But, someone else will have to do that. The last time I made a pull request on this package it was rejected for spam (pull requests generate emails, although I don't think I have control over that). If I could control whether people are liking or not, I would (likes also generate emails), but maybe the package maintainer can take it up? Not sure. In any event, I just use my fork with upstream to the main and that works for my purposes.
That said, I haven't tested custom user models, but I'm fairly certain the above approach should work in these circumstances.
You might also need to do this forms.py as well, by the way.