Accessing request object in django urls.py

No, You can't.

The as_view() accepts any class attributes of a view class. In your case, the request object will not accessible from the class

class Foo(ListView):
    queryset = Question.objects.filter(user__id=request.user.id)

The above snippet you can't reference the request and hence also in your urls.py

In these kinds of complex situations, we should override the get_queryset(), as you know.

You normally do this by overriding the get_queryset method in a subclass of the ListView. So you can create a view:

# app/views.py

from django.contrib.auth.mixins import LoginRequiredMixin
from django.views.generic.list import ListView
from app.models import Question

class QuestionListView(LoginRequiredMixin, ListView):
    model = Question
    template_name='testapp/question_list.html'
    context_object_name='questions'

    def get_queryset(self, *args, **kwargs):
        return super().get_queryset(*args, **kwargs).filter(
            user_id=self.request.user.id
        )

In the urls.py you then use the QuestionListView

# app/urls.py

from django.urls import path
from app.views import QuestionListView

urlpatterns += [
    path('myqn/', QuestionListView.as_view(), name='myqn'),
]

You can define a function or lambda expression with:

import inspect

def custom_queryset(*args, **kwargs):
    self = inspect.currentframe().f_back.f_locals['self']
    return Question.objects.filter(
        user_id=self.request.user.id
    )

urlpatterns += [
    path('myqn/', QuestionListView.as_view(get_queryset=custom_queryset), name='myqn'),
]

This is however not a good idea. First of all, it inspects the call stack, and if later the ListView is altered, it might not work anymore. Furthermore here this listview will not check if the user has logged in for example. We can not make use of the method resolution order (MRO) to make a call to a super() method.

---

Note: You can limit views to a class-based view to authenticated users with the LoginRequiredMixin mixin [Django-doc].