Hey All, I appreciate the inputs.
A couple of clarifications. - I developed the plugin based on my experience with nosetest and pytest while teaching a software testing course. I plan to use it in the future editions of the course. For this purpose, the plugin suffices in its current form -- features and distribution. - The intention to move to pytest-dev is not to off load maintenance. I plan to maintain the plugin. [It is so simple :)] - Since verdicts are core of xunit frameworks, I figured having pytest-finer-verdicts as a default plugin might be useful to others; even if it needs to enabled explicitly (via CLI options). - IIRC, the plugin is really four lines of modification to pytest_runtest_makereport function in pytest. It was set up this way as this was the best way (I could figure out) to inject the desired functionality into pytest. All said, I am fine to wait for wider adoption of the plugin before we integrate it into pytest. I am fine if we want leave it as non-default plugin. I understand and respect these decisions. So, for now, I'll shelf this issue (and withdraw my request) until there is interest from the community. Cheers, Venkatesh-Prasad Ranganath http://about.me/rvprasad On Mon, Jun 27, 2016 at 9:20 AM, holger krekel <[email protected]> wrote: > On Mon, Jun 27, 2016 at 10:21 +0200, Ronny Pfannschmidt wrote: > > Hello Venkatesh-Prasad and Florian, > > > > as of now the linked plugin is basically a really new plugin, which is a > > 20 line function without any tests. > > as such i would like to postpone moving it into pytest-dev until it is > > more widely used and has a proper test-suite. > > > > we want to have pytest-dev as a place to put popular plugins in order to > > ease and open up maintenance and share control, > > we might want to have a different place for the public/shared incubation > > of plugins and experiments. > > -- Ronny > > I see it similarly. Also, i'd like to note that in my view submitting a > plugin to pytest-dev does not imply that it will be maintained by > "others" from then on. Rather contributing a plugin usually means > continuing to care for it and collaborating on pytest core issues and, as > ronny > mentions, sharing commit and release control to reduce bus factors etc. > > holger > > > > > > > Am 26.06.2016 um 18:54 schrieb Venkatesh Prasad Ranganath: > > > Hey Florian, > > > > > > I can look into tox.ini and longer description in setup.py. > > > > > > As for changed behavior, would providing a CLI option to activate the > > > plugin suffice? > > > > > > Venkatesh-Prasad Ranganath > > > http://about.me/rvprasad > > > > > > On Sat, Jun 25, 2016 at 11:27 AM, Venkatesh Prasad Ranganath > > > <[email protected] <mailto:[email protected]>> wrote: > > > > > > Hey All, > > > > > > What is the process to make this happen? Is the first step to > > > transfer pytest-finer-verdicts > > > <https://github.com/rvprasad/pytest-finer-verdicts> to pytest-dev > > > organization? If so, please consider this email as the request > > > for transfer. > > > > > > Cheers, > > > > > > Venkatesh-Prasad Ranganath > > > http://about.me/rvprasad > > > > > > > > > > > > > > > _______________________________________________ > > > pytest-dev mailing list > > > [email protected] > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > _______________________________________________ > > pytest-dev mailing list > > [email protected] > > https://mail.python.org/mailman/listinfo/pytest-dev > >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
