Context Navigation

Changes between Version 2 and Version 3 of Ticket #37165

v2	v3
3	3	The main problems are:
4	4
5		1. It strongly implies that Django's asynchronous story is unfinished. It's often liked to in blog posts. And it's totally misleading. The user API is essentially finished. From the PR: """Many parts of Django provide asynchronous APIs, including :ref:`the ORM <async-queries>`, the cache framework, authentication, sessions, mail, and signals. For other code, the :func:`sync_to_async` adapter is a low-cost bridge (see :ref:`async_performance`)."""
	5	1. It strongly implies that Django's asynchronous story is unfinished. It's often linked to in blog posts. And it's totally misleading. The user API is essentially finished. From the PR: """Many parts of Django provide asynchronous APIs, including :ref:`the ORM <async-queries>`, the cache framework, authentication, sessions, mail, and signals. For other code, the :func:`sync_to_async` adapter is a low-cost bridge (see :ref:`async_performance`)."""
6	6
7	7	2. The performance warnings are severely outdated. `sync_to_async`/`async_to_sync` usage is in the order or microseconds with modern versions of Python. This plays directly into implementation considerations where we're constantly pulled towards duplicating whole code trees, on the mistaken assumption that `sync_to_async` usage (in particular) incurs a (relatively) massive performance hit.