> > I don't think it makes a significant difference from a readability > perspective in this example. It does have some advantages, though: > > - It could be easier to implement a sync version based on the async one, > or vice-versa, if each one has its own class. It will probably be more DRY. > - It could also be a bit more usable by developers, especially in IDEs >
Speaking about convenience, it would be great if we could make the sync versions raise exceptions when used with an event loop attached and the async ones fail when there isn't a loop running. I assume synchronous views would be executed within a worker thread with the event loop explicitly set to None. -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5b6222c3-9f76-4eb3-8619-e3f44a17d6a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
