#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

The From idea to production video demo which demonstrates in a stunning a 12 minute video how to deploy GitLab on OpenShift, then login to GitLab and create a project with a pipeline that deploys the project on OpenShift itself.

“How to make a navigation autocomplete with django-autocomplete-light v3” seems like a top FAQ since v3 release, because v2 included an example which was not reported inside the documentation of v3.

While the example in v2 documentation is still valid, the autocomplete.js script was removed from django-autocomplete-light, and is now available in the jquery-autocomplete-light repository.

Happy hollidays from the YourLabs panarchy :)

Django 1.11 alpha is announced for January 16, review priority will be given to any ticket marked “ready for checkin” by January 9, Tim says, which means its still time to make a contribution to Django 1.11 !

The only “major feature” on the 1.11 roadmap is template-based widget re ndering which is (hopefully) in final reviews. There are still plenty of “patches needing review” if you want to help there.

My personnal advice ? Try to do even just a small contribution or try to help reviewing, it’s still time ;)

We have two major features:

• Advanced field forward options,
• List based autocompletion.

Complete changelog:

• #745: Add list autocomplete by @dmosberger, https://github.com/jpic and https://github.com/thecardcheat,
• #754: dal_queryset_sequence documentation update by @chubz
• #734: Move create_option functionality into it’s own method @andybak
• #741: Fix initial value not set when selected choices aren’t strings @thauk-copperleaf
• #733: Advanced forward features @gagarski
• #752: Add doc test to CI by @jpic
• #730: Resolve SystemCheckError fields.E304 @thecardcheat
• #721: Note about placement of DAL before grappelli by @chubz
• #748: Update docs example about loading jquery outside the admin @jpic

This release includes a bugfix for the new feature added in 0.7.0, occuring with non-ascii characters in selector-based tests with python 2.

Fix by @njoyard, test case by @jpic.