Matthew Schinckel

The latter - to come up with a proper solution.

That's fine, but what if you have a reusable app that does/doesn't, and you use that in your project that has the other setting?

Whilst it is documented, I found it surprising (and not easy to work around). I'd support it being the default that it does not include disabled valves.

Does this require a new migration?

I believe this is because the function that sniffs the frame for the filename fails to work on a template render - it seems that the `self` object in the...

I'll create a PR shortly, but my patch seems to work (waiting on a CI run to check). ```diff @@ -104,5 +104,15 @@ def filename_for_frame(frame): try: - return frame.f_locals["self"].origin.name -...

When I have a model that has an admin interface registered, and I run test with —coverage, then I get an AlreadyRegistered exception: Traceback (most recent call last): File "./manage.py",...

My workaround was to ignore all exceptions when importing for coverage checking.

Gah. I don't have 3.3 installed locally.

Yes, I just noticed that branch-coverage (as coverage.py calls it) is not reported upon.