Django反向解析pt-detail路由触发NoReverseMatch报错问题排查

已配置的代码片段 #

路由配置 #

urlpatterns = [
    # 论文项目模块路由
    path('create-paper-project/', PTCreateView.as_view(), name='pt-create'),
    path('list-paper-projects/', PTListView.as_view(), name='pt-list'),
    path('pproj<str:pk>/', PTDetailView.as_view(), name='pt-detail'),
    path('pprojp<str:pk>/update/', PTUpdateView.as_view(), name='pt-update'),
    path('pproj<str:pk>/delete/', PTDeleteView.as_view(), name='pt-delete'),
]

类视图配置 #

class PTCreateView(generic.CreateView):
    model = PaperTool
    template_name = 'papertools/pt_create.html'
    success_url = '/paper-tools/list-paper-projects/'
    fields = ['title']

class PTListView(generic.ListView):
    model = PaperTool
    template_name = 'papertools/pt_list.html'

    def get_context_data(self, **kwargs):
        context = super().get_context_data(**kwargs)
        return context

class PTDetailView(generic.DetailView):
    model = PaperTool
    template_name = 'papertools/pt_detail.html'

    def get_context_data(self, **kwargs):
        context = super().get_context_data(**kwargs)
        return context

class PTUpdateView(generic.UpdateView):
    model = PaperTool
    fields = ['title']
    template_name = 'papertools/pt_update.html'
    success_url = reverse_lazy('paper:pt-detail', kwargs={'pk': model.pk})

class PTDeleteView(generic.DeleteView):
    model = PaperTool
    template_name = 'papertools/pt_delete.html'
    success_url = reverse_lazy('paper:pt-detail')

模板代码片段 #

<a class="nav-link" href="{% url 'pt-detail' object_list.paper.pk %}">
    Paper Project Home
</a>

实际触发的报错 #

Reverse for 'pt-detail' with arguments '('',)' not found. 1 pattern(s) tried: ['paper-tools/pproj(?P[^/]+)/$']

已验证的测试结论 #

• 把模板中反向解析传入的object_list.paper.pk替换为固定有效主键（例如数值6），反向解析可正常运行
• 替换其他任意合法主键值，均可正常匹配对应路由
• 仅当传入object_list.paper.pk时触发上述报错，公开技术社区暂未检索到完全匹配的同类场景解决方案

问题根因 #

• 模板变量层级错位：PTListView作为PaperTool模型的列表视图，传入模板的object_list是模型实例组成的查询集，本身不存在paper关联属性，顺着object_list.paper.pk取值最终得到空字符串，与报错中传入空参数的现象完全吻合
• 类视图跳转配置硬伤：
  • PTUpdateView在类属性定义阶段直接引用model.pk，此时视图还未处理具体请求流程，根本拿不到当前操作对象的主键值，运行时必然触发错误
  • PTDeleteView反向解析pt-detail路由时，未传入路由要求的必填pk参数，就算路由名匹配成功，也会因参数缺失触发解析报错
• 命名空间引用不匹配：如果当前路由是挂载在paper命名空间下的，模板中反向解析时缺少命名空间前缀，会进一步导致路由匹配失败，增加排查难度

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