Hi all, currently when a model signal receiver is registered with an
abstract model as the sender, we allow it even though the receiver will
never be called. It would be nice if the signal registry wasn't polluted by
bogus entries that will never be used.
A few options:
a) Make passing an abstrac
Just a reminder the today is the last day to register for DjangoCon at
Early Bird rates. Tomorrow, prices will increase by $50 per ticket. To
register, click here:
https://2016.djangocon.us/tickets/
Prices are affordable for the 5 days, starting at $195 for our diversity
rate. The speakers lin
Sorry, but this post without any explanation doesn't help much.
For usage questions, please use the django-users mailing list. To report
bugs, use https://code.djangoproject.com/.
On Tuesday, May 31, 2016 at 8:26:41 AM UTC-4, L K Singh wrote:
>
> class AccountTypeSerializer(serializers.ModelSer
This feature is tracked in https://code.djangoproject.com/ticket/8936. Feel
free to review, contribute to, or test the patch if you want to help.
On Tuesday, May 31, 2016 at 8:26:41 AM UTC-4, Ander Ustarroz wrote:
>
> I am surprised this feature is not implemented yet, at the moment when we
> cr
class AccountTypeSerializer(serializers.ModelSerializer):
parent =
serializers.PrimaryKeyRelatedField(queryset=AccountType.objects.all(),
required=False)
class Meta:
model = AccountType
fields = ('id','parent','account_type_name')
--
You received this message because y
I am surprised this feature is not implemented yet, at the moment when we
create a new model three permissions are created automatically for the
admin panel:
- *add_permission*
- *change_permission*
-
*delete_permission *
We really missing the *view_permission* here, when we want sta
