Description
For 95% of projects that may theoretically use this package, this is fine. Most Django projects will have some form of login-wall, probably have some form of permission checks, and thus require user objects to handle. Furthermore, it's rare that these projects will use session handling logic that isn't Django's default built-in.
However, for all other projects (such as using this package to test other packages), this may not be desired functionality. For example, the DjangoDumpDie Package does not need or know of Users/sessions at all. So for testing this DumpDie package, it doesn't make sense to force either to be present. But ExpandedTestCases currently forces it to be.
In the future, we probably want some handling to check if session middleware is present. Also settings to be able to toggle "default user generation". For the moment, this is fairly low priority.