Dan Fairs
Dan Fairs
Sorry for not responding sooner, github mails go into a bit of a black hole for me :( I've reproduced this locally and will push a fix over the next...
Reopening because I haven’t fixed it yet :)
Looks fine, could you add a quick test to make sure that the request is being passed please? (Also, can I confirm that the tests don't pass with this change...
Thanks for your PR! Two comments, really: - Could you refactor the PR to avoid all the duplicated code? Most of that new code is the same as `allow_lazy_user`. Pull...
(Oh - and sorry for the delay - all my GH notifications are going astray at the moment, and I'm trying to figure out why...)
The way to do this right now is to either: - subclass LazyUserManager and override `generate_username`, and set that as the manager on `LazyUser` - If you've got a custom...
Hm, that does look like a bug. You might be able to work around it temporarily by disabling your custom user, running the migrations, re-enabling it and generating the required...
Yes, that's almost certainly related. `lazysignup` predates the custom user support in Django, and I've never really had time to work support into `lazysignup` properly.
Hi there - thanks for this! I haven't had time to check this out yet, but I notice it's causing the Travis build to fail. I think it worked before...
Right, that all makes sense. I guess we may need to do something clever with `manage.py` to make it compatible with both, perhaps a (nasty) version check or something.