If I had to guess, it would be that with more than one leaf node, you would
end up a substantial challenge resolving dependancies which would create an
Order(N) problem (i.e. there's a chance of excessive time to complete the
resolution).
I certainly worked on some migration logic that took a s
NY
>> order in the graph, that it would still give me the same result, for
>> example:
>>
>> [ 0001_initial ] => [ 0002_auto ] => [ 0003_def ] => [ 0003_abc ] => [
>> 0004_auto ]
>>
>>
>> Please let me know if I’m missing something, ideas
] => [ 0002_auto ] => [ 0003_def ] => [ 0003_abc ] => [
>>> 0004_auto ]
>>>
>>>
>>> Please let me know if I’m missing something, ideas and thoughts are
>>> really welcome :)
>>>
>>>
>>> [1]
>>> https://github.com/django/d
FYI
Sent from my iPhone
> On 22 Apr 2020, at 18:23, Brian Tiemann wrote:
>
>
> Hi all,
>
> I was directed here after getting corroboration on #django and elsewhere.
>
> I have what appears to be a bug in which a Django app can deadlock if you hit
> it with a lot (>3) of AJAX requests with
Sorry - that message was sent as a 'reply' in error - my colleague uses
ajax with Django a lot and I was trying to forward this to him.
Kind Regards,
Dave
On Wed, 22 Apr 2020 at 18:23, Brian Tiemann wrote:
> Hi all,
>
> I was directed here after getting corroboration on #django and elsewhere.
+1, I'd happily help on any PR with this (it would be my first!).
Kind Regards,
Dave
Springbourne Tech Limited
M: +44(0) 79 2107 6483
W: www.springbourne-tech.com
*—This E-Mail and its contents are confidential, protected by law
and legally privileged. Only access by the addressee is autho
Hi Shai,
If you used '<{0} id="{1}"> {2} '.format(tag, id, content) in a
templatetag (for example), it could easily be used iteratively which would
increase the need for performance and at that point, you could argue that
f'<{tag} id="{id}"> {content} ' would be a preferable choice, even
though y
