On projects I've been working on I started using "prettier" fro JavaScript
and it made a huge difference to code consistency across the team, which
was great, but my favourite benefit (that I'm not sure I've seen mentioned
much here) is I can write code faster if I don't have to format it. Being
ab
We ran into this issue a couple of months ago - I'm not sure how helpful
this is but just in case extra information is useful I'll share our
workarounds. The faulthandler output was roughly the same - the error
happened during a rollback. This also happened on multiple python and
sqlite versions.
I meant jQuery 2 and 1.11 are API compatible - you're right though, the
latest versions of jQuery might have deprecated things that are currently
used in Django.
On Wed, 19 Aug 2015 at 10:39 elky wrote:
>
> On Wednesday, 19 August 2015 14:27:53 UTC+5, sdcooke wrote:
>>
>> and get the performance
For jQuery support in older browsers it's pretty simple to include jQuery
1.11 in old IE using conditional comments - that way we retain support with
just an extra line of code, don't leave IE8 behind, and get the performance
boost of jQuery 2 in modern browsers. As far as I'm aware they are still
Hi all,
I've had experience playing around with watchdog[1] before - I've only ever
used it on OS X but it should work cross platform. I've thrown together a
rough proof of concept[2] for runserver that uses watchdog to watch for
changes/additions/deletions to python files recursively in the same
ri, 13 Mar 2015 at 21:40 Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> 2015-03-13 12:21 GMT+01:00 Sam Cooke :
>
>> The test template we were using to test the performance was a simple:
>> {% for item in item_list %}{% include "item.html" %}{% endfo
Preston - I'll send the template to you directly, I'm not sure how useful
it will be so I don't want to spend time checking if it's fine for public
consumption unnecessarily.
The test template we were using to test the performance was a simple:
{% for item in item_list %}{% include "item.html" %}
I've done a couple of days of investigation into template performance
recently trying to speed up our site and my main takeaway was that there
was no silver bullet - no particular node taking up all of the time. I was
mostly trying to optimise a particularly complicated template we render a
lot in
