Closed ukch closed 9 years ago
@ukch To confirm - are we talking about class-based-views or something else?
These are a form of class-based views, but different to the 'Django generic' ones. These are called using the __call__
method.
Not sure if supporting non-standard view setups is a good plan or not. I guess at the least we ought to verify that it doesn't break anything with eg how CBVs are currently handled.
A good point. I will check how this affects views that use the as_view
method (the django.views.generic
way of doing things).
@tomchristie I have ditched my previous attempt and have made a new fix using a try/except block instead.
@ukch Just taking a look at this, if you're still interested in trying to get it work. It looks like it's still failing, since the instance of ProductSearchView
doesn't have a __name__
attribute, which gets referenced on line 70 so we can print it later.
Given how old this PR is, and that it currently doesn't work, I'm going to close it for now. Feel free to open another one.
When debugging instance-based views (such as those from django-haystack), a traceback is encountered:
To fix this error, inspect the class instead of the instance.