You don't use things on PyPI anyway. You may install them from there, but pip will install Github-, Bitbucket-, anywhere-else-you-want-hosted packages just fine. Or you can just put the package on your system and install it from there. Or even put the app in your site-packages folder yourself!

Take a break, get your anger under control, and then find a solution to your problem instead of rage-quitting a framework for something that's not even remotely the framework's fault.

As others have said, there are plenty of other solutions: use a fork of django-registration, fork django-registration yourself and use that, django-userena, django-allauth, django-socialauth, django-authtools, etc etc etc.

Erh? This post would be funny were it not so pathetic. By which I mean, this would be like refusing to go to the Grand Prix because one of the hot dog stands outside was giving out the wrong brand of ketchup. Don't get me wrong, that guy shouldn't be such a dick about this, but arguing that its a valid reason to not use django is just straight up preposterous. It just sounds like you have your knickers in a bunch and this is just venting. Seriously, if this were a valid reason not to use django then it would also be a valid reason not to use any framework of this nature, because these "problems" are not unique to Django.

Without resorting to the same level of vitriol that you have spewed, I would like to question your understanding of Django and the Django ecosystem. I think your anger/hate stems from your belief that django-registration is a core part of Django.

Not so.

django-registration, as so many of the others have pointed out, is just a third-party app developed and maintained by a developer. He does not seem to be a core-part of the Django team, nor does he make any claims of the sort. Nor does he claim that django-registrations is a part of the core Django installation. [EDIT: As /u/huxley1970 pointed out to me, James has indeed been a part of the core Django team since 2006. Apologies for the wrong information.]

As for his interactions - well, I will neither approve nor condemn them. It is, after all, an app HE has developed and provided it to you for free and that too, open-source. If you want to change something, you can always clone it, modify it and use your cloned git repo for the egg, instead of the standard PyPI install.

As an example, if a third-party plugin for WordPress were broken, would you rage on WordPress? If a game/app for Facebook were not working, would you rage on Facebook?

I understand that the developer's behavior may have irked you. Rather than rage on the platform and the community, ask us for options - there are a lot of people who will be happy to provide you with those. For instance, I've tried django-userena and it works absolutely great! It even comes with a contrib uMessage system that allows you to setup messaging between your users.

I understand the rage, what I don't understand is the direction you aimed it at.