A presentation by James Pic, founder of YourLabs, was filmed at djangocong 2016 Rennes: video (french) slides (english) docs to reproduce demo source code

An interresting series about reverse engineering has been posted by Juan Carlos Jiménez.

django-autocomplete-light v3.1.6 was released, thanks to these fine contributions: #671: Create_field support with querysetsequence by @jpic #679: Allow create message translation by @maisim #682: Extend ‘forward’ attribute to creating objects as well by @toudi #666: Improved missing ‘created_field’ error by @guettli #670: Javascript loading documentation by @jpic #678: Added example to update autocompletes in JS by @jpic

ZNet explains Invisible Programming Language and Invisible Data Theft , the new threat on the internet.

This release enables field-forwarding in formsets and forms with prefix. Also note that several things have been made to help users: a new tutorial section showing placeholder and minimum-input-length select2 options has been added and a system check will raise an error if select2’s js is not present - typically for users who have git clone’d the repo without --recursive, resulting in a wc without select2. For devs, we’ve moved from django-sbo-selenium to pytest+splinter and it’s pretty cool ! Read More

This release provides commit e612748 which fixes a bug in the TaggitSelect2 to reproduce the bugfix in 15f27871 that was issued in 3.1.2.

django-dbdiff was released. It allows to exclude fields from tests with the new exclude parameter, ie:: Fixture( 'tweets/tests/after_create_retweet.json', models=[Tweet, Retweets], ).assertNoDiff( exclude={ 'tweets.tweet': ['datetime'], 'tweets.retweets': ['datetime'], }, } This was initially requested by Nicolas Joyard for the Political Memory project. Note that you shouldn’t use exclude for datetimes like in the above example, but instead use something like freezegun to force datetimes to an arbitrary fixture.

This posts announces the release of django-autocomplete-light 3.1.2: #634: Select2 Upgrade #628: Do not rely on ids to fix container text #631: Initializing GFKs with values from forms #623: Fix setup.py extras by @ticosax #610: Cancel out Django’s style on lists Enjoy B)

Currently, django-autocomplete-light v2 provides enhancement to default form field generation for model fields, depending on the registered autocompletes, as shown in the tutorial. For v3, we don’t want this feature inside DAL anymore because it has really nothing to do with autocomplete. Instead, I’m trying to contribute a generic way to do that. It would not benefit only django-autocomplete-light anymore, but all Django apps. You could get enhanced default form fields for model fields just by installing and configuring apps in your project. Read More

This post clarifies the status of django-autocomplete-light and strategy for v3. Version 2 No further effort will be made to support new versions of Django in v2. However, it supports the current LTS Django 1.8 and future-release Django 1.10, so we’ve got plenty of time to re-do v2’s best features in v3 (in a better way) and most importantly you’ve got plenty of time to upgrade (until 2018). Version 3 It’s a ground-up rewrite and it’s not backward compatible - hence the 2 years upgrade plan. Read More