#22806: Some lookups/transforms don't have lookup_name
--------------------------------------+------------------------------------
Reporter: jorgecarleitao | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: invalid
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 mjtamlyn):
* status: new => closed
* resolution: => invalid
Comment:
OK, I'm going to close this for now as I don't think it is an issue in
this case. If someone has a genuine use case then we can add it, but I
believe the way they are written means they cannot be used directly with
`register_lookup` because their `__init__` signature is wrong - you need
the factory.
--
Ticket URL: <https://code.djangoproject.com/ticket/22806#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.e03ef79eab204ce25beebb75e7f910d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
