Matt Hegarty

Hi Manel. I might have misunderstood the issue, so please feel free to correct me. Are you able to reproduce it using the example app? I think I have been...

OK no problem. I'll be interested to see more detail about your issue, because I guess adding `default` to `Field()` doesn't solve it?

Hi @stfl - thanks for submitting this. Is it possible you could supply suitable test cases?

Thanks Stefan - this would go into our `release-3-x` branch - so I suggest you merge that branch into yours. I'll change the base for the PR.

My only concern with this is that there may be some users who are expecting `ObjectDoesNotExist` to be thrown from `resources.py`, and that they may be catching this in their...

@pokken-magic would appreciate your input as you raised #1447

Thanks for submitting this PR - I'll review in detail when I get a chance. > Should this be based to the v3-release branch instead? Yes I think that if...

I think we'll need to take a step back and try to understand exactly what's going on before we can merge. From what I have read from previous issues, the...

I added the following to `tests/core/admin.py`: ```python @receiver(post_save, sender=Author) def post_save_callback(sender, **kwargs): print("Save called") ``` I then imported the attached Author via the Example App. With this fix we would...

AFAIK, [setting a flag on the instance](https://stackoverflow.com/a/71625152/39296) would be the only way to prevent the `post_save` signal being called twice.