Re: [Django] #35413: FieldError: Unsupported lookup error message can be confusing. (was: FieldError: Unsupported lookup error message can be confusing on DateTimeField)

[Django]

#35413: FieldError: Unsupported lookup error message can be confusing.
-------------------------------------+-------------------------------------
Reporter: Alex | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

* stage: Unreviewed => Accepted
* summary:
FieldError: Unsupported lookup error message can be confusing on
DateTimeField
=> FieldError: Unsupported lookup error message can be confusing.
* type: Bug => Cleanup/optimization

Comment:

Replicated, this is also true of other fields.
I agree that saying something like `Unsupported lookup 'gt__foo'`,
`Unsupported lookup 'gt__'`, and `Unsupported lookup 'gt__lt'` would be
clearer.
--
Ticket URL: <https://code.djangoproject.com/ticket/35413#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.