<div dir="ltr">Hi Holger,<div><br></div><div>I've played around a bit with PyPi's api.</div><div><br></div><div>Obtaining the meta data is easy enough, but I found that only 7 out of 60 of the packages (searching for "pytest-") have a tox.ini file. Even thought it is just a few, I think we can use that initially especially if that encourages more plugin authors to use tox to manage its test runs.<br>
</div><div><br></div><div>I'm thinking of putting a script that can generate Sphinx docs from live PyPi package information, and later on be also able to test plugins compatibility. I'm thinking to provide a patch to pytest's own documentation, but later on we can move this to a live app that periodically fetches that information to keep it up to date if you think it is necessary. How does that sound?</div>
<div><br></div><div>Cheers,</div><div>Bruno</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 4, 2013 at 7:18 PM, holger krekel <span dir="ltr"><<a href="mailto:holger@merlinux.eu" target="_blank">holger@merlinux.eu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Oct 04, 2013 at 18:43 -0300, Bruno Oliveira wrote:<br>
> But even just collecting the other information i mentioned (without<br>
> > the test status / running questions) would already be helpful, btw.<br>
> ><br>
><br>
> That seems simple enough, a script that queries pypi and extracts this<br>
> information could be used to generate a page and/or statistics.<br>
><br>
> >From my understanding you would like a page to accomplish two things:<br>
><br>
> 1. A list of known py-test plugins and their py27/py33 status.<br>
> 2. If the plugins work against latest pytest and against trunk, so pytest<br>
> developers know if they're breaking existing plugins (intentionally or not).<br>
><br>
> Is that correct?<br>
<br>
</div>yes. Along with repo information (probably not easy to automatically<br>
detect but doesn't change often so once manually is fine).<br>
<div class="im"><br>
> I'm trying to figure out a semi automatic way to accomplish both. :)<br>
<br>
</div>You can use pypixmlrpc, maybe, to get at meta info (but not something<br>
like repository).<br>
<br>
cheers,<br>
holger<br>
<div class="HOEnZb"><div class="h5"><br>
> Cheers,<br>
> Bruno<br>
><br>
><br>
> > cheers,<br>
> > holger<br>
> ><br>
> > > The other part is how to present this info, but e.g. a CSV file<br>
> > > > can be rendered by sphinx and the main docs could include it<br>
> > > > or we make a separate page if need be.<br>
> > ><br>
> > ><br>
> > > > thanks for considering to help!<br>
> > > ><br>
> > ><br>
> > > Glad to. :)<br>
> > ><br>
> > > Best Regards,<br>
> > > Bruno<br>
> > ><br>
> > > ><br>
> > > > holger<br>
> > > ><br>
> > > > > Cheers,<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > On Fri, Oct 4, 2013 at 10:09 AM, holger krekel <<a href="mailto:holger@merlinux.eu">holger@merlinux.eu</a>><br>
> > > > wrote:<br>
> > > > ><br>
> > > > > ><br>
> > > > > > I just did three pytest plugin releases to get out a few minor<br>
> > > > > > fixes and improvements. see below. As far as i am aware most<br>
> > > > > > existing plugins (as well as the new releases here) should be<br>
> > > > > > compatible to pytest-2.4.2. Some plugins like pytest-capturelog<br>
> > > > > > have seen their latest release three years ago but remain<br>
> > functional.<br>
> > > > > > A good sign that the plugin system is reasonable i guess.<br>
> > > > > ><br>
> > > > > > If someone wants to help with organizing plugin compatibility<br>
> > > > > > tests and maintaining a status page, i'd really appreciate that.<br>
> > > > > > With over 50 existing plugins it's not easy to stay on top.<br>
> > > > > > The current <a href="http://pytest.org" target="_blank">pytest.org</a> page is only a start:<br>
> > > > > ><br>
> > > > > > <a href="http://pytest.org/latest/plugins.html#extplugins" target="_blank">http://pytest.org/latest/plugins.html#extplugins</a><br>
> > > > > ><br>
> > > > > > and here is the full pypi list:<br>
> > > > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > ><br>
> > <a href="https://pypi.python.org/pypi?%3Aaction=search&term=pytest-&submit=search" target="_blank">https://pypi.python.org/pypi?%3Aaction=search&term=pytest-&submit=search</a><br>
> > > > > ><br>
> > > > > > there are also some github/bitbucket-only plugins, in addition.<br>
> > > > > ><br>
> > > > > > And finally a note to plugin authors: please be subscribed<br>
> > > > > > to pytest-dev and post new plugin releases here.<br>
> > > > > ><br>
> > > > > > best,<br>
> > > > > > holger<br>
> > > > > ><br>
> > > > > > pytest-xdist-1.9:<br>
> > > > > ><br>
> > > > > > - changed LICENSE to MIT<br>
> > > > > ><br>
> > > > > > - fix duplicate reported test ids with --looponfailing<br>
> > > > > > (thanks Jeremy Thurgood)<br>
> > > > > ><br>
> > > > > > - fix pytest issue41: re-run tests on all file changes, not just<br>
> > > > > > randomly select ones like .py/.c.<br>
> > > > > ><br>
> > > > > > - fix pytest issue347: slaves running on top of Python3.2<br>
> > > > > > will set PYTHONDONTWRITEYBTECODE to 1 to avoid import concurrency<br>
> > > > > > bugs.<br>
> > > > > ><br>
> > > > > > pytest-xprocess-0.8:<br>
> > > > > ><br>
> > > > > > - support python3 (tested on linux/win32)<br>
> > > > > ><br>
> > > > > > - split out pytest independent process support into xprocess.py<br>
> > > > > ><br>
> > > > > > - add info.kill() method and some smaller refactoring<br>
> > > > > ><br>
> > > > > > - fix various windows related Popen / killing details<br>
> > > > > ><br>
> > > > > > - add tests<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > pytest-pep8:<br>
> > > > > ><br>
> > > > > > - use pytest-2.4.2 node.add_marker() API for adding "pep8" marker<br>
> > > > > ><br>
> > > > > > _______________________________________________<br>
> > > > > > Pytest-dev mailing list<br>
> > > > > > <a href="mailto:Pytest-dev@python.org">Pytest-dev@python.org</a><br>
> > > > > > <a href="https://mail.python.org/mailman/listinfo/pytest-dev" target="_blank">https://mail.python.org/mailman/listinfo/pytest-dev</a><br>
> > > > > ><br>
> > > ><br>
> ><br>
</div></div></blockquote></div><br></div>