id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
26470	Checks performed during Permission creation should use the check framework.	Simon Charette	nobody	"The `django.contrib.auth.management.check_permission` function that is connected to the `post_migrate` signal performs static model analysis checks that should rely on the check framework. At the moment a `ValidationError` or a `CommandError` is raised when a check fails.

The checks performed are the following:

1. Check that custom permissions don't clash with built-ins and are not duplicated;
2. Check that models `verbose_name` doesn't exceed a certain length based on the `Permission.name.max_length`;
3. Check that permissions `name` doesn't exceed a certain length based on the `Permission.name.max_length`.

For `2.` and `3.` I suggest we make them issue a `check.Warning` with a message noting that the name will be truncated to N characters instead of crashing with an `IntegrityError` if the check is ignored/disabled."	Cleanup/optimization	closed	contrib.auth	dev	Normal	fixed			Ready for checkin	1	0	0	0	0	0