Thanks for your help
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To
So new iOS and Mac minor versions were launched, but issue is still there.
Created a new bug ticket on Webkit and they're being able to reproduce
better the problem: https://bugs.webkit.org/show_bug.cgi?id=196375
Hope they can reach a solution soon!
Florian, you mean a blog post on Django's blog
Thank you! I'll share my proposal here when I'm done with my first draft.
On Thursday, 28 March 2019 21:49:36 UTC+7, Carlton Gibson wrote:
>
> Hi Sage.
>
> Yes. It never hurts to apply. If we get two good proposals for the same
> project, we can find a way to share or another project.
> We can
Hi Sage.
Yes. It never hurts to apply. If we get two good proposals for the same
project, we can find a way to share or another project.
We can cross that bridge as and when we come to it.
("Scale later" )
Kind Regards,
Carlton
On Thursday, 28 March 2019 14:58:15 UTC+1, Sage M.A. wrote:
Hi everyone,
Sorry to ask this, but can I also take a shot in this one? I've been
interested in this issue since early February.
On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>
> Also, sorry, this was the key thread here, plus links therein
>
Hi Parth,
Yes, something along those lines will be right.
First-off, what are the existing work-arounds (i.e. how are people handling
this in the wild: overriding `__init__()` methods etc...) — can these be
summarised and documented, where worth recommending?
Then, API changes to improve on
