Ronny Pfannschmidt
Ronny Pfannschmidt
@spearsem the technical best practice is - libraries don't set up logging on import, applications set up logging on startup and that prevents a number of issues - like triggering...
Pytest probably needs to warn every time a log handler does the "crime" of setting up stdio handlers in test setup
https://github.com/pytest-dev/pytest/blob/c326c0449433ff812e1b3b81b2590f0d1d797fde/src/_pytest/main.py#L255-L311 we pretty much dont handle exceptons from that particualr hook on a sidenote, i also beleive its not expected that it causes issues in the form of exceptions -...
conftests are only ever searched locally, so unless you put evil magic in your tests folders you shouldnt see this
After the 20th I'm happy to volunteer, after all I skipped the honour for a while now
@jaraco recently created the pytest-enabler plugin
note, this should be a opt in via config, potentially by naming a policy, as dropping everything passed by default changes the debug-ability when one wants to compare passed stuff...
Let's think a bit more about what variants we want, then we can pick a name
nothing yet, however i haven't yet put my thoughts onto having `tmp_dir` as session and module/package scope fixture yet
The proposal is only about the policy but for finding a good name im thinking about a future change /feature