On Fri, Sep 25, 2015 at 14:40 +0200, Ronny Pfannschmidt wrote: > I think we should deal with logging in core, since its in the stdlib
I am fine with both -- leaving pytest-catchlog as 3rd party or integrating it into core. FWIW pytest's release speed is not that bad especially as we are automating it further and more people can do the releasing. FWIW i think "catchlog" is a somewhat bad name. Why not just "pytest-logging" and move it to pytest-dev? holger > Am 25. September 2015 14:16:20 MESZ, schrieb Bruno Oliveira > <[email protected]>: > >On Fri, Sep 25, 2015 at 9:03 AM Florian Bruhin <[email protected]> > >wrote: > > > >> As I said there, I'm actually not sure if it should be merged, or at > >> least not yet - it's finally starting to have some bugfixes and > >> features compared to capturelog, and I plan to contribute some more > >> stuff I need when I switched over (which will be when that PR is > >> merged). Having an independent plugin release cycle has its benefits, > >> after all... > >> > > > >I agree. I think the main motivation for merging was that it was a > >widely > >used plugin which was unfortunately not maintained anymore. Since this > >is > >no longer the case, I also wonder if perhaps leaving it as a separate > >plugin would be better. :) > > > >Cheers, > >Bruno. > > > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >pytest-dev mailing list > >[email protected] > >https://mail.python.org/mailman/listinfo/pytest-dev > > MFG Ronny > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev > -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
