One of my long time fascinations has been with data compression. I've read a
lot about it, tried to keep up with modern techniques, but never really written
much usable code.
Recently I decided, partly as an exercise in remaining fluent in C, I'd try to
re-implement one of the simplest algorithms I know. I used this method almost
20 years ago to compress payloads for a tiny embedded board which had 256kB RAM
and 128kB ROM.
So, 4 years ago [already??] I wrote a post about a shortcut to getting "User
registration with verification email", using very little code by leveraging the
password reset machinery built into Django.
Since then, of course, Django has moved on... and recently, the auth views were
rewritten as class-based views, which changes the game entirely.
As a result, I've committed to providing here an updated version of the
Some years ago, I adapted the work of a coworker and released it as
django-classy-settings, a way to define Django settings using a class,
allowing a clean and easy way to derive local / production settings from a
common base, and opening the way to allowing composition, too.
Recently I was faced with a similar problem at my current job, though not using
Django this time.
Another big difference is my current job is using Python3.6 (and eager to move
to 3.7 ASAP), opening other opportunities.
I've recently started teaching myself an interesting language I discovered on
the LLVM project page : Pony
First, I tried rewriting keyster - a
simple Key/Value store that talks over UDP.
Every so often (quite frequently, actually) you'll get someone in #django
begging for help trying to integrate some app that promises the world ... at
least, as far as it concerns user registration and profiles.
A couple of people pointed out the original version would end up requiring the user to enter their email twice.
I've now amended the code so the password_reset view's work is now done in the registration CreateView.
This makes the view a little more complicated, but the URLs and user workflow much simpler.
The thing is, now that we have custom User models, doing this is easier than
ever before - yes, even including email verification.