| 7 | | Another way to see it is that `staticfiles` checks could perform access control gated I/O to determine if they are properly setup (e.g. has access to local or remote destination) some model checks and we don't treat them differently. The fact this was surfaced as a potential problem here is that `SimpleTestCase` was used to avoid database queries and previously the suite of checks performed by default didn't access the database. The thing is even if Django passes `databases=None` or doesn't call tests tagged with `Tag.database` it cannot guarantee that the check it calls actually don't access the database, it just happened to be the case within Django core for a long time. |
| | 7 | Another way to see it is that `staticfiles` checks could perform access control gated I/O to determine if they are properly setup (e.g. has access to local or remote destination) like model checks do against the database and we don't treat them differently. |
| | 8 | |
| | 9 | The fact this was surfaced as a potential problem here is that `SimpleTestCase` was used to avoid database queries and previously the suite of checks performed by default didn't access the database. The thing is even if Django passes `databases=None` or doesn't call tests tagged with `Tag.database` it cannot guarantee that the check it calls actually don't access the database, it just happened to be the case within Django core for a long time. |