Re: A Django Async Roadmap

The DEP is drafted and in the DEPs repo, and awaiting approval by the freshly-elected Technical Board once I submit it. In the meantime, we landed the ASGI patch, as well. Andrew On Tue, Jun 25, 2019 at 3:30 PM Chris Barry wrote: > Hey all, > > Just wondering what the future of this is looking

Re: A Django Async Roadmap

Hey all, Just wondering what the future of this is looking like? CB On Friday, 12 April 2019 07:33:35 UTC+1, Shaggy wrote: > > and how it is going ? > is there some interest from django devs? > > On Monday, 4 June 2018 15:18:23 UTC+2, Andrew Godwin wrote: >> >> Hello everyone, >> >> For a while

Re: A Django Async Roadmap

and how it is going ? is there some interest from django devs? On Monday, 4 June 2018 15:18:23 UTC+2, Andrew Godwin wrote: > > Hello everyone, > > For a while now I have been working on potential plans for making Django > async-capable, and I finally have a plan I am reasonably happy with and >

Re: A Django Async Roadmap

If you're following that 'medium' article, then you'll see it uses https://github.com/jneight/django-db-geventpool, which has instructions for using `psycogreen` with gunicorn... I believe what it states is correct. On Thursday, December 13, 2018 at 3:21:32 AM UTC, Ray Marceau wrote: > > James

Re: A Django Async Roadmap

James Addison, I also currently use `psycogreen.gevent` for postgresql async behaviour. > How did you go about using psycogreen.gevent for async postgres? I tried using various tools and was unsuccessful in seeing any performance improvements. I was following the info here: https://medium.

Re: A Django Async Roadmap

On Monday, June 4, 2018 at 6:18:23 AM UTC-7, Andrew Godwin wrote: > > For a while now I have been working on potential plans for making Django > async-capable, and I finally have a plan I am reasonably happy with and > which I think we can actually do. > Andrew, Out of curiosity, how would thes

Re: A Django Async Roadmap

AFAICT the performance hit is minimal unless you are doing something slow when logging warnings (e.g. -Walways with a slow I/O py.warnings handler). The Python/Django instrumentation simply adds a value to Model._state and look it up on attribute accesses. Cheers, Simon Le lundi 20 août 2018 19

Re: A Django Async Roadmap

In general this sounds like a tremendously useful tool... I'm caused to wonder, however... what, if any, are the performance impacts? -- Curtis On 08/21/2018 08:10 AM, charettes wrote: Regarding the lazy loading of deferred fields and foreign keys I wanted to mention I've been working on a t

Re: A Django Async Roadmap

Regarding the lazy loading of deferred fields and foreign keys I wanted to mention I've been working on a third-party application that allows overriding the default behavior[0]. The project works by tainting objects retrieved from "sealed" querysets and having fields descriptors lookup whether or

Re: A Django Async Roadmap

I just wanted to add that I'm really excited for this change. On PyCon Sweden 2015 I held a "Why Django Sucks"-presentation where I talked about where the web is heading, and why django is lagging behind. The main point was lack of support for async. After the presentation lots of people came

Re: A Django Async Roadmap

On Fri, Jun 8, 2018 at 11:31 PM Josh Smeaton wrote: > > The only real concern I have at the moment is around your comments > regarding on demand foreign key traversal. If existing code running > synchronously is going to be impacted, that's going to be very difficult > for a lot of people. If it'

Re: A Django Async Roadmap

> Loading a lazy ForeignKey/RelatedField attribute on a model instance Also deferred fields. -- 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

Re: A Django Async Roadmap

I think most of what you've laid out sounds great and that pursuing async Django is in the projects best interests. The sync to async and async to sync wrappers that have come out of channels give me much more confidence that this project is doable in a reasonable amount of time with backwards

Re: A Django Async Roadmap

Chaim: For references to get up to speed on async concepts, there's not a lot of great beginner-level stuff out there. I have a practical guide to async functionality at https://www.aeracode.org/2018/02/19/python-async-simplified/, but it's not great at going into detail on Web stuff and why it has

Re: A Django Async Roadmap

The proposal looks great, thanks for putting it together and pushing async in Django forward. I'm not sure the best approach to take here, but I've just started experimenting on a fork: https://github.com/erm/django/tree/async-experiment-2. I am unsure how much of the more complex items I may

Re: A Django Async Roadmap

I wonder if a sensible first tack onto this might be: Supporting an ASGI/asyncio request-response cycle in 2.2 might be a perfectly achievable goal with or without funding. Users wouldn't be able to use the ORM, or much of the default middleware, but for some gateway-type services I can still

Re: A Django Async Roadmap

> Unfortunately even if you have context variables, you simply can't await inside of an attribute reference because there's a synchronous call in your stack. I even chatted to some Python core devs at PyCon US about this and we couldn't really think of a way out of this problem without some very se

Re: A Django Async Roadmap

I'm really excited that the django community is starting to think of async-friendly django. I think this is needed for the community and will be a strenght point for the framework itself for next couple of years if this will take place. Now that asyncio is a thing in the Python world I think mor

Re: A Django Async Roadmap

Andrew, I don't know enough about async web to comment directly on your proposal, but like most of your proposals it looks well thought out and comprehensive. Kudos to you. As you state, the scope of this project is one that can raise the profile of developers in the community - that appeals t

Re: A Django Async Roadmap

> > > I think getting rid of the related field references could be a big issue > here and cause a lot of headaches for existing applications. Could we do > this in a backwards compatible way at all? I wonder if PEP 567 > could help here, could we > define

Re: A Django Async Roadmap

On 06/05/2018 07:54 AM, Tom Forbes wrote: Are the proposed modifications to how Django runs sensible? I had a few random thoughts while reading your proposal: I think getting rid of the related field references could be a big issue here and cause a lot of headaches for existing applicatio

Re: A Django Async Roadmap

Hey Andrew, thank you for the very exciting proposal and the ongoing work on Django channels! There is a lot to consider here and some very interesting problems to work through - I’d love to help out wherever I can. Do we think async is worth going after? I think this is very much worth doing. As

Re: A Django Async Roadmap

> Do we think async is worth going after? I think this is hugely important. Django's advantage in the field currently is in it's developer productivity and maintainability. As frameworks based on Node or on languages with co-operative concurrency built-in continue to mature it's going to face m

Re: A Django Async Roadmap

Hello Andrew. I like your proposal and want to help out. In particular, what I'm really fond of is the approach of making async available only if you want it, while keeping Django backwards-compatible. Django is brilliant in that, like the Python language, it's easy and fun to pick and learn, but

A Django Async Roadmap

Hello everyone, For a while now I have been working on potential plans for making Django async-capable, and I finally have a plan I am reasonably happy with and which I think we can actually do. This proposed roadmap, in its great length, is here: https://www.aeracode.org/2018/06/04/django-async