DEP 9: Please do not ignore the async-only usecase

[django]

DEP 9: Please do not ignore the async-only usecase

[andrewgodwin]

Hi - this is not the appropriate place to discuss a DEP, please instead raise it on the django-developers mailing list.

However, I do want to say that your use case is what I'm aiming for anyway - namely, that the two modes are async-only (async mode) and sync with some async (sync mode). If you run async code in Django when DEP is finished, there'll be no sync code running in the same stack.

[abetkin]

@andrewgodwin Thanks for your answer. I see that it is one of eventual goals of DEP 9, I think that will be enough. Not sure now if it makes sense to raise this on django mailing lists, since it's not directly related to DEP 9. This is not a DEP too, since most work on enabling async-only usecase, if not all, can be done in a third-party package. And since nothing stops anyone from implementing this, it may be a more reasonable thing than discussing. The enabling of async usecase is gradual effort as well: over time, more and more configuration/code could be shared between the traditional and async django. Btw, is the current implementation code of DEP 9 public?

[andrewgodwin]

DEP 9 is not a single implementation; it's ongoing. The current part of it that is in progress is in django/django#11650