In above code, If a user calls `foo/`, following AttributeError will be
raised.
`Generic detail view FooUpdateView must be called with either an object pk
or a slug in the URLconf.`
FooUpdateView raises the error even though it isn't generic detail view.
Also CreateView has this issue because it inherits from SingleObjectMixin.
--
Ticket URL: <https://code.djangoproject.com/ticket/30030>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: oliver => oliver
* has_patch: 0 => 1
Comment:
https://github.com/django/django/pull/10742
--
Ticket URL: <https://code.djangoproject.com/ticket/30030#comment:1>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/30030#comment:2>
* status: assigned => closed
* resolution: => wontfix
Comment:
The error message here has been unchanged since class-based views were
first introduced in 0fcb09455729113f64a9873ca40bffd009b9bc5f#diff-
e67e689265faab47842e64d6c8c564ddR40.
The phrasing "generic detail view" captures not a specific view class but
the group of all descendants of `SingleObjectMixin` (otherwise it would be
`GenericDetailView`...) There are (I think) 11 of those. It reflects the
`view.generic.detail` module naming. I think it's fine vs the proposed
`that inherits from SingleObjectMixin` alteration.
--
Ticket URL: <https://code.djangoproject.com/ticket/30030#comment:3>