>
>
> - I dislike the seetings approach of GLOBAL_PERMS and would rather see 
>   users writing explicit data migrations. 
>

I don't favour either setting or migration based perms, but if you're going 
to go with migration based, then please also consider adding a first class 
permission type, to avoid the ceremony of creating forward/back functions, 
and having to remember the model layout for Permissions.

Something like:

migrations.CreatePermission(app_label, permission_name)

or django.contrib.auth.CreatePermission (which is actually an Operation) if 
we want to avoid contrib polluting migrations proper. 

I haven't fully thought through the implications, but every time I need to 
write a data migration I spend more time than I'd like to admit searching 
for a previous data migration from which to copy.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/32bb32b4-bf1a-494e-8588-df70f8abfef7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to