Michal Petrucha

I've created a trivial test case that reproduces the issue (at least the way I'm experiencing it): https://github.com/pytest-dev/pytest-django/compare/master...koniiiik:589-mailoutbox-is-not-django-core-mail-outbox?expand=1

You are absolutely right, it does appear that mutability got the better of me, it is indeed the case that I was modifying the list in place, rather than assigning...

I don't think `modify_settings` is applicable, it is just a convenience specialization that simplifies the handling of settings that take lists. In this case, if we want to detect mutations...

Adding some more details that I managed to find out by poking around the code. Apparently, the object that fails to get pickled by dill is the `out` attribute of...

I might be misunderstanding something, but I don't see the problem with this conflict – if `-w` is provided on the command line, it takes precedence, and if it's not...

I have done some more testing with the change I proposed in #8903, and when running just the daemon, and interacting with it over the RPC, everything seems fine. I...

And I can also add another case that triggers the same false positive – methods on the model class itself: ``` class A(models.Model): field = models.DateTimeField(auto_now=True) def b(self): return self.field.isoformat(timespec='seconds')...

This is one of the possible symptoms of the issue that was fixed in #577.

I have now spent some time looking into this issue, and as far as I can tell, the `restart` option of `depends_on` only applies to the `docker compose restart` command....

There's no indication that this has been addressed in any way. (I hope we don't have to play the stale / bump game every few months for years from here...