Peter Bittner

Alright, so if that's the problem we have to reset the settings value in `after_scenario`. It's not too hard to do with such a decorator: ``` python @override_settings(DEBUG=True) def before_scenario(context,...

No offence, please. Decorators are no magic, it's a wrapper function. If I do dirty stuff in its implementation the result will stay dirty, won't it? It may be _meant_...

We should agree that we are talking about behave-django. I'm not referring to `django.test` since https://github.com/behave/behave-django/issues/13#issuecomment-286802925 onwards. Technically, it's certainly possible to make things more elegant than today.

I'm not sure why using `--simple` should result in a different behavior with fixtures. For what I understand from the documentation and source code there should be no reason why...

For some reason, the [tests that cover fixture loading](https://github.com/behave/behave-django/blob/master/tests/acceptance/features/fixture-decorator.feature#L1) specify a `@requires-live-http` decorator. @sebastianmanger, @mixxorz, does one of you happen to remember why?

@sebastianmanger @mixxorz ***ping*** :bell:

Huuu-huuu, @sebastianmanger! :santa: Ho-ho-ho, @mixxorz! :mrs_claus: Any idea how we can explain the behavior? :bell:

So, the behavior of `--simple` is buggy and we need to fix it, is this correct? Let me summarize: 1. We want `--simple` to behave the same way as "non-simple"...

I added a note to the project's documentation, as the suggested. Visible in the [latest docs](https://behave-django.readthedocs.io/en/latest/isolation.html) for now, until the next release. **EDIT:** This shouldn't be the end of the...

> The problem may be that part of the logging statement locations are in `behave-django` Not sure that we do anything with logging. All that `behave-django` does is make sure...