* holger krekel <[email protected]> [2015-11-09 08:52:15 +0000]: > On Mon, Nov 09, 2015 at 06:24 +0100, Florian Bruhin wrote: > > Hey, > > > > * Florian Bruhin <[email protected]> [2015-10-20 06:20:42 +0200]: > > > * Arthur Skowronek <[email protected]> [2015-10-19 23:17:24 +0200]: > > > > It would be nice if the plugin could stay separated from the core > > > > package. > > > > At least I am a huge fan of the modular plugin system as it can be > > > > found in > > > > pytest. I find such a modular design more preferable compared to a > > > > monolithic project that comes with everything attached. Such a large > > > > project > > > > makes it harder for users to track what was changed between versions and > > > > keep track of changes important to them. They don't need to care at > > > > all if > > > > the API was changed but they don't use the plugin. > > > > > > > > Also different contributors stated that they still would like to > > > > improve the > > > > code base and add more functionality. It would be nice to give them > > > > their > > > > freedom to break the API if necessary to create something even more > > > > usable > > > > with a sleeker API. I'm looking forward to it. > > > > > > I used to have a different stance on this - but after reconsidering, I > > > agree it'd be best to have a "recommended" plugin (i.e. catchlog, as > > > it's maintained and under pytest-dev) rather than merge things into > > > core. > > > > Backwards compatibility is restored and eisensheng released 1.2.0 - so > > I think everything is ready to move pytest-catchlog to pytest-dev now. > > > > Of course +1 from my side - any objections and/or a second +1 please? > > ;) > > I noticed that there now also is a pytest-logging release from Pedro Algarvio: > > https://pypi.python.org/pypi/pytest-logging > > which adds to the confusion around logging and pytest, unfortunately. > > I haven't used pytest-catchlog myself yet but intend to do so. > It'd be great if eisenheng or you could get in contact with Pedro > and see how we can all arrive in a situation which is less confusing > to users, somewhat independently from the question of merging catchlog > into pytest-dev.
Fun! It seems that plugin simply adds --logging-format and --logging-date-format options, and configures the verbosity based on -v: https://github.com/saltstack/pytest-logging/blob/master/pytest_logging/plugin.py I opened an issue there discussing merging it into pytest-catchlog: https://github.com/saltstack/pytest-logging/issues/1 Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: Digital signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
