One quick clarification - when I said "stable (1.0)" release, I in fact
meant the first release that the Black project officially marks as stable.
Black doesn't use versioning that would result in a stable release being
called 1.0, as far as I know, given they are on 19.3b0 right now!
Andrew
O
Hi everyone,
The Technical Board has voted on DEP 0008 (
https://github.com/django/deps/blob/master/accepted/0008-black.rst), after
the extensive discussion here and the updates done as a result.
The board voted in favour, and so I've moved the DEP into the accepted
directory.
One of the key cha
On Fri, May 10, 2019 at 3:51 AM Asif Saif Uddin wrote:
> I have a separate question. Is it possible to get the django 3.0 asgi
> things into a different package to use with django 2.2?
>
> Thanks for the great work.
>
>
Unfortunately not - this is covered a little in the section in the DEP that
s
I have a separate question. Is it possible to get the django 3.0 asgi
things into a different package to use with django 2.2?
Thanks for the great work.
On Friday, May 10, 2019 at 3:42:08 PM UTC+6, Patryk Zawadzki wrote:
>
> We've always considered that implicit queries on attribute access were
>
> We've always considered that implicit queries on attribute access were an
> intractable problem. I said it on stage an DjangoCon US 2013. I'm now
> wondering if I was wrong all along! In an async ORM context, every time we
> traverse a relation, we could create a Future that would execute t