#26470: Checks performed during Permission creation should use the check
framework.
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* stage: Unreviewed => Ready for checkin
Comment:
Those checks were added before the permission name `max_length` was
increased from 50 to 255 (#8162). Therefore I expect few if any users to
exceed that limit these days. I don't see much benefit to adding
truncation logic as proposed.
--
Ticket URL: <https://code.djangoproject.com/ticket/26470#comment:2>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.7b5bb2448a38524efb143781724b84d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
