Well, it definitely stands for something ! And since this is becoming a FAQ, here’s my answer:

It stands for: Create Read Update Delete Form Autocomplete and more !

We started by making a CRUD because the customer was complaining his come was not DRY and that we should have a CRUD in Django - the customer comes from the modern PHP framework world.

We soon figured we needed a crudL, for the list. We wanted to add custom actions with custom forms and it became crudlF because we added the FormViewMixin. Then we wanted to add automatic autocomplete views so it became crudlfA, with the AutocompleteView (to be Open Sourced soonish). Then we wanted to just refactor custom views: turned out into we use ModelViewMixin, the mixin for a model view, ie. list, create … and ObjectViewMixin, mixin for a model instance view ie. detail update delete forms …

You can install it with:

pip install django==2.0a1

Time to test some apps

With <3

This is a quick video I made so our friends can see CRUDLFA+, the DRY framework for Django, looks like so far:

With <3

Jamesy aka jpic

This all started when a web developer learning Django was struggling to maintain a quantity of HTML and came to me: “I have a question for you, Django, can you generate a menu for me please ?”.

Oh my, is this person going to be the next wasting their time building something that’s too complicated and worthless just like I have back when I used to try this kind of stunt ?

django-autocomplete-light 3.2.6 was released on github and pypi, with:

#838: Use namespaced jQuery in `get_forwards` by @ryan-copperleaf & @gagarski
#836: Queryset sequence view to display actual model name by @jsoa

3.2.5 and 3.2.6 were briefly hosted on PyPi and are the same.

Enjoy <3

#813: Return 400 on invalid input by @EvaSDK

3.2.3 Two seriously good community contributed bugfixes

• #799: Support serializing UUIDs and add tests for models with UUIDs as PKs by @blag
• #826: Prevent rendering of empty option on multi select by @beruic

Bravo !

Tests are passing reliabily these days. The code climate is pretty sunny to contribute patches.

Help wanted on unit tests: there is a bunch of units and currently everything is tested together with selenium. This works but that means when we test django 1.8 to 1.12 (master, not passing) we need to run selenium much more (for each version) than if we had unit tests covering the code. It would make following up Python and Django versions easier.

django-autocomplete-light 3.2.2 was released, it supports django 1.11 and is not known to break backward compatibility.

Let’s give a warm welcome to django-session-security’s new release manager, Erik Telepovský from pragmaticmates.com.

DSS release 2.5.0 was published in PyPi:

• #79 remove compiled binary from source to comply with Debian source code repository policy by @nirgal
• #81 support django 1.10 by @eriktelepovsky
• #84 a11y support to modal dialog by @lynnco
• #85 support for mobile device activity by @kalekseev
• #88 dutch translation update by @rdekker1
• #91 test django 1.11 and 2.0 instead of 1.7 by @jpic
• Rename default branch to master