Hi everyone, Unfortunately pytest's 3.1 warning capture being active by default has caused grief on some test suites and there's been a lengthy discussion about it on this thread:
https://github.com/pytest-dev/pytest/issues/2430 I'm pointing this out here so others can join the discussion and share their thoughts. Also, I'm wondering what should be our next course of action on this. Should we make a new release (3.1.1, 3.2, 4.0?) where this feature is opt-in or if by now it is too late to revert it given that those affected might have already fixed their suites. As a lesson learned here I'm starting to think that we should from now on always introduce new features as opt-in, and if we want to change the defaults do so only on a major release. Would love to hear everyone's opinion on this. Cheers, Bruno.
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
