If you do want to update it then there's a version I'm using with Django
1.6 and Python 3.4 here: https://github.com/macropin/django-registration.
Might be a good start.
On Saturday, 2 August 2014 19:03:01 UTC+2, Aymeric Augustin wrote:
>
> On 2 août 2014, at 18:08, Tim G
On 2 août 2014, at 18:08, Tim Graham wrote:
> On a related note, djangoproject.com depends on django-registration so we
> need to update it for 1.7 compatibility or remove the dependency.
Then our most reasonable option is to fork it under django/django-registration,
isn't it?
Oh
On a related note, djangoproject.com depends on django-registration so we
need to update it for 1.7 compatibility or remove the dependency.
On Friday, August 1, 2014 6:13:34 PM UTC-4, James Bennett wrote:
>
> Speaking for myself, I am still willing to hand over the reins of
&g
Speaking for myself, I am still willing to hand over the reins of
django-registration to someone who's genuinely motivated to try to solve
the issues surrounding things like custom User support, etc., though I
still do believe that's just a bridge too far for what was meant to be a
o a system. Why provide that when some
> people might not want a site with authentication, or might want to do it
> through Facebook or OpenID? (Or, as per your reference to James' reasons,
> Persona?)
>
I think the difference between django-registration and South is that
there is
What no one is discussing here is is that django-registration is just one
out of several popular authentication backends that match it for use and
great exceed it's functionality. They include:
* django-allauth
* django-userena
* python-social-auth (nee django-social-auth)
These three pro
It seems to me, in any case, the first step is to get django-registration
actively maintained again. James Bennett is welcoming proposals of people
to take over maintenance of the project. Get it working well with custom
user models and with python 3. Once django-registration is a thriving app
mplete? No. Is it perfect? Definitely not. But it's damn
good for a significant number of use cases, and that is why it is still
part of core.
For what it's worth, I have used django-registration much more frequently
than I have used the admin, and I'm willing to bet that's the
eblog/2013/aug/26/catching/
>
> Any Django site that uses a database will benefit from integrating
> database migrations. On the other hand, there are many ways to do user
> registration (as James described in his post) so django-registration isn't
> a 90% use case that qual
his post) so django-registration isn't a 90% use
case that qualifies for inclusion in contrib.
On Friday, August 1, 2014 9:02:54 AM UTC-4, Robert Grant wrote:
>
> Hi Tim
>
> Thanks for the reply. I'd say that it's only been viable so far because
> James created and m
gt;
> If no one has volunteered to maintain it in nearly a year since James
> stepped down, I think you'll have a tough time convincing us it's important
> enough to move into contrib. Also, the recent trend has been to remove
> things from contrib (comments, localflavor, form
eally
> enjoying using it; thank you.
>
> I'm using Django 1.6 and Python 3.4. For user signups, everyone recommends
> using django-registration. However this is not under active development
> <https://bitbucket.org/ubernostrum/django-registration/wiki/Home> (still
&
Hello all
I've just started using Django for a serious project and am really enjoying
using it; thank you.
I'm using Django 1.6 and Python 3.4. For user signups, everyone recommends
using django-registration. However this is not under active development
<https://bitbucket.or
Jeremy Dunck said the following:
> On Dec 28, 2007 11:35 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>> I'm happy to take care of this -- I just don't know what's involved in
>> registering a channel. Could you provide some more information on whom
>> to talk to about getting it done?
>
> http
On Dec 28, 2007 2:38 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On Dec 28, 2007 11:35 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > I'm happy to take care of this -- I just don't know what's involved in
> > registering a channel. Could you provide some more information on whom
> > to
On Dec 28, 2007 11:35 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I'm happy to take care of this -- I just don't know what's involved in
> registering a channel. Could you provide some more information on whom
> to talk to about getting it done?
>
http://freenode.net/group_registration.sht
On Dec 28, 2007 1:06 AM, Collin Grady <[EMAIL PROTECTED]> wrote:
> I've never bothered bringing this up before as it's never really been
> needed, but tonight we had someone with a rogue script in their IRC
> client which prevented them from closing their client, and flooded the
> channel with "he
On 28 Dec 2007, at 7:06 am, Collin Grady wrote:
>
> I've never bothered bringing this up before as it's never really been
> needed, but tonight we had someone with a rogue script in their IRC
> client which prevented them from closing their client, and flooded the
> channel with "hello world" fo
I've never bothered bringing this up before as it's never really been
needed, but tonight we had someone with a rogue script in their IRC
client which prevented them from closing their client, and flooded the
channel with "hello world" for a minute and a half solid :)
It would've been very helpfu
19 matches
Mail list logo
