It looks like the settings don't always get properly reset between individual unit tests. This is generally not a problem, but the cached JINJA_ENV property does seem to create some very strange behavior. Simply removing the @cached_property decorator doesn't work - it causes even more weirdness. I need to look more deeply into what's going on.
It looks like the settings don't always get properly reset between individual unit tests. This is generally not a problem, but the cached JINJA_ENV property does seem to create some very strange behavior. Simply removing the @cached_property decorator doesn't work - it causes even more weirdness. I need to look more deeply into what's going on.