Django 4.1异步视图调用request.user触发SynchronousOnlyOperation错误

我用以下异步代码检查用户是否is_authenticated：

async def offers(request, currency_id):
    user = await User.objects.aget(pk=request.user.pk)
    currency = await sync_to_async(get_object_or_404)(Currency, pk=currency_id)
    offers_to_sell = [
        item
        async for item in Offer.objects.filter(
            currency_to_sell_id=currency_id
        ).prefetch_related("currency_to_sell", "currency_to_buy")
    ]
    context = {"currency": currency, "offers_to_sell": offers_to_sell, "user": user}
    return render(request, template_name="offers.html", context=context)

但触发了如下错误：

SynchronousOnlyOperation 
You cannot call this from an async context - use a thread or sync_to_async.

Traceback (most recent call last):
  File "\venv\lib\site-packages\django\contrib\sessions\backends\base.py", line 187, in _get_session
    return self._session_cache

我还尝试了以下代码，但仍未解决：

user = await sync_to_async(User.objects.get)(pk=request.user.pk)

以及在模板中直接使用：

{% if request.user.is_authenticated %}

结果依旧报错，我似乎忽略了异步调用的某些要点，请问问题出在哪里？

核心问题 #

错误根源是在异步视图中直接访问request.user——Django的request.user是同步属性，内部依赖会话（session）的同步操作，在异步上下文里直接调用会触发SynchronousOnlyOperation错误。你之前的尝试只处理了User查询，但没解决request.user.pk这步的同步调用问题。

具体解决步骤 #

1. 用sync_to_async封装request.user的访问
   先把获取用户ID的操作放到同步线程里执行，避免在异步上下文直接碰request.user：

   from django.utils.decorators import sync_to_async
   
   async def offers(request, currency_id):
       # 先通过sync_to_async获取用户ID
       user_id = await sync_to_async(lambda: request.user.pk)()
       # 再用异步查询获取用户对象
       user = await User.objects.aget(pk=user_id)
       
       currency = await sync_to_async(get_object_or_404)(Currency, pk=currency_id)
       offers_to_sell = [
           item
           async for item in Offer.objects.filter(
               currency_to_sell_id=currency_id
           ).prefetch_related("currency_to_sell", "currency_to_buy")
       ]
       context = {"currency": currency, "offers_to_sell": offers_to_sell, "user": user}
       return render(request, template_name="offers.html", context=context)
   

2. 模板中使用request.user的正确姿势
   模板里直接用request.user.is_authenticated也会触发同样问题，因为模板渲染时还是会同步访问request.user。解决办法：

   • 提前在视图中计算好认证状态，放到context里传给模板：

     # 在视图中添加
     is_authenticated = await sync_to_async(lambda: request.user.is_authenticated)()
     context["is_authenticated"] = is_authenticated
     

     模板里改成：

     {% if is_authenticated %}
     

   • 或者用sync_to_async封装整个模板渲染操作（第一种方式更轻量）。

3. 额外优化：避免重复查询用户
   其实不需要重新查询User对象——如果只是要判断认证状态或获取用户基本信息，直接通过sync_to_async封装request.user的访问即可，不用再查一次数据库：

   async def offers(request, currency_id):
       # 直接获取完整的user对象（同步操作封装）
       user = await sync_to_async(lambda: request.user)()
       # 后续可以直接用user.is_authenticated等属性
       
       currency = await sync_to_async(get_object_or_404)(Currency, pk=currency_id)
       offers_to_sell = [
           item
           async for item in Offer.objects.filter(
               currency_to_sell_id=currency_id
           ).prefetch_related("currency_to_sell", "currency_to_buy")
       ]
       context = {"currency": currency, "offers_to_sell": offers_to_sell, "user": user}
       return render(request, template_name="offers.html", context=context)
   

关键知识点 #

Django的异步视图中，所有涉及会话、认证的同步属性（比如request.user、request.session）都不能直接访问，必须用sync_to_async封装，因为这些操作底层依赖同步的数据库/缓存调用，无法在异步事件循环中直接执行。

内容的提问来源于stack exchange，提问作者Vitalii Mytenko