I’m pretty lazy when it comes to writing tests for existing code, however, I’m even lazier when it comes to repetitive manual testing action, catching up with untested legacy code when I want a lot of coverage now, at least to ease upstream dependency upgrade testing.

PHPUnit has had a DBUnit component since at least 10 years, and Junit too, I ported the concept to Django, first in several apps. Extracted it in the package to de-duplicating the data import tests from django-representatives and django-representatives-votes which is re-used in django-cities-light.

Django-autocomplete-light 3.3.0-rc3 was released.

Please try it out and submit feedback !

With LOVE

jpic

To install 3.3.0-rc1, use:

pip install django-autocomplete-light==3.3.0-rc1

New features:

• @953: Select2 update to 3.4.0.6-rc.1 by @jpic
• @917: django-nested-admin support by @loicteixeira
• @815: Simplify customization of autocomplete views by @EvaSDK
• @746: Select2 Language and dynamic Media by @luzfcb
• @883: Allow overwriting the results by @eayin2

Bug fixes:

• @874: Fix Django 1.11.3 error by @ikcam
• @933: Python 3.6 and Django 2.0 support by @jpic
• @930: QuerySetSequence querysets order is not preserved by @melvyn-sopacua
• @909: Prevent initilization of other selects by @loicteixeira
• @904: Fix KeyError when id is not in attrs by @dwheaton
• @885: Prevent rendering of empty option on multi select by @johandc
• @892: Enable different item label for selected item by @maximpetrov
• @926: Atomic create_object by @jpic
• @718: Remove temp hack for select2 by @FuzzAU
• @860: dal: widgets: use the name if we don’t have the id by @xrmx
• @849: Don’t create a new option if an iexact-matching one already exists by @liwenyip

Also thanks to the many documentation contributors.

Hello everybody, This month we have made a thousand euro donation to the Red Cross, to help refugees arriving in Europe, please, consider making a donation yourself. With LOVE

Dvorak-intl-code is a keyboard layout optimized for polyglot hackers I’ve started working on and using in 2008.

This article demonstrates how to easily create your own keyboard layout by extending an existing one, storing your config in your home directory and load it with a command which .xinitrc or whatever can call.

Just add a file in ~/.xkb/symbols, for example I put mine in /home/jpic/.xkb/symbols/code, and looks as such:

// Dvorak variant for polyglot coder

Which may save quite some SLOCs (Single Line Of Code)

Curry is nothing more than a function returning a function to call a function

Hello everybody <3

Let’s talk about ideas for deprecation / discouraging the use of get_context_data().

get_context_data() is useful to support legacy templates from the pre-CBV era, since CBV we can now access any attributes from the view instance with {{ view }}.

I’ve seen things like this in many projects, I wonder if it’s the case for other people too:

def get_context_data(self, **kwargs):
    c = super().get_context_data(**kwargs)
    c['something'] = self.something
    return c

And I’m guilty as charged you can find commits from myself like this all over internet.

Next CRUDLFA+ version with Materializecss preview !

https://www.patreon.com/materialize?utm_medium=social&utm_source=yourlabs&utm_campaign=plshare

Yessss! We are now a proud patron of Alan and Alvin on @Patreon, and you should be too ;) With LOVE

https://docs.google.com/document/d/1C-ceqQ3UxvURLPsMxd5Ej658ETuwxEK4hElKafwBsyQ/edit

What my work looked like in 2013 (French).