#32695: Create Permissions with create() instead of bulk_create() to send signal
-------------------------------------+-------------------------------------
Reporter: BRISBOIS Laurent | Owner: BRISBOIS
Type: | Laurent
Cleanup/optimization | Status: closed
Component: contrib.auth | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
Comment:
> But what if people need to react on this (in my opinion) important step
which is the creation of the Permissions?
I think it's really niche because no one has reported this in the last 10
years. You should be able to add e.g. a `post_migrate` handler or a
scheduler job and check for new permissions. You can also try to ask for
alternatives on one of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels]. I don't think this is worth changing at the moment.
Moreover, as far as I'm aware your issue will be fixed by #29843, which
propose including permissions in migrations files.
--
Ticket URL: <https://code.djangoproject.com/ticket/32695#comment:8>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.e38e0badd28fbb4ce3a8ff1eae212bd1%40djangoproject.com.
