[pytest-dev] sorting out broken config initialization - by doing major releases with api breakages

Floris Bruynooghe flub at devork.be
Tue Aug 21 17:02:37 EDT 2018

On Tue 21 Aug 2018 at 11:03 -0300, Bruno Oliveira wrote:
> Personally my next goal is the task to replace the internal warnings system
> to use the standard warnings module, which I should be able to tackle soon
> as I have some vacation time coming up, but after that I'm happy to help
> with the configuration refactoring.

Hum, have you successfully used the stdlib warning module in such a
fashion in another project before?  I recall trying to do this many
years ago but concluding that the stdlib warnings system is there not
for your code but for Python itself.  And especially with respect to
testing I recall that it was deliberate not to use this since it would
make testing code which uses warnings even more tricky.

But it's quite likely that my opinion is somewhat out of date and you've
actually got good reason for this.


More information about the pytest-dev mailing list