Hi! I'm part of the pytest-dev team, the developers of the pytest[1] test runner. I'm writing to you because I'd like to have some opinions on the following PR/issue about vendoring pluggy into pytest:
https://github.com/pytest-dev/pytest/issues/944 https://github.com/pytest-dev/pytest/pull/959 The common logic behind the plugin API of pytest recently got split into a separate library, pluggy[2]. However, the public API of pluggy might still change in the near future - which means pytest would need to require a specific version of pluggy to be sure there's no breakage. Normally, this wouldn't be an issue - but as a test runner, I believe we're in a bit of a special position: Users should still be able to use pytest to test their projects, even if their projects use a more recent version of pluggy - or they use other projects which might use pluggy in the future, like devpi or tox. Because of this, since it's a very small library, and because the code originated from pytest, I wonder what distribution's views are on bundling the library for pytest 2.8 until things are expected to be a bit more stable. What do you think? Florian [1] http://www.pytest.org/ [2] https://github.com/hpk42/pluggy -- 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/
pgp4WiZuNLOlt.pgp
Description: PGP signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
