[pytest-dev] (new) pytest plugins / note to plugin authors

[Bruno Oliveira]

Hi Holger,

I've played around a bit with PyPi's api.

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.

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?

Cheers,
Bruno


On Fri, Oct 4, 2013 at 7:18 PM, holger krekel <holger at merlinux.eu> wrote:

> On Fri, Oct 04, 2013 at 18:43 -0300, Bruno Oliveira wrote:
> > But even just collecting the other information i mentioned (without
> > > the test status / running questions) would already be helpful, btw.
> > >
> >
> > That seems simple enough, a script that queries pypi and extracts this
> > information could be used to generate a page and/or statistics.
> >
> > >From my understanding you would like a page to accomplish two things:
> >
> > 1. A list of known py-test plugins and their py27/py33 status.
> > 2. If the plugins work against latest pytest and against trunk, so pytest
> > developers know if they're breaking existing plugins (intentionally or
> not).
> >
> > Is that correct?
>
> yes.  Along with repo information (probably not easy to automatically
> detect but doesn't change often so once manually is fine).
>
> > I'm trying to figure out a semi automatic way to accomplish both. :)
>
> You can use pypixmlrpc, maybe, to get at meta info (but not something
> like repository).
>
> cheers,
> holger
>
> > Cheers,
> > Bruno
> >
> >
> > > cheers,
> > > holger
> > >
> > > > The other part is how to present this info, but e.g. a CSV file
> > > > > can be rendered by sphinx and the main docs could include it
> > > > > or we make a separate page if need be.
> > > >
> > > >
> > > > > thanks for considering to help!
> > > > >
> > > >
> > > > Glad to. :)
> > > >
> > > > Best Regards,
> > > > Bruno
> > > >
> > > > >
> > > > > holger
> > > > >
> > > > > > Cheers,
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Oct 4, 2013 at 10:09 AM, holger krekel <
> holger at merlinux.eu>
> > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > > I just did three pytest plugin releases to get out a few minor
> > > > > > > fixes and improvements. see below.  As far as i am aware most
> > > > > > > existing plugins (as well as the new releases here) should be
> > > > > > > compatible to pytest-2.4.2.  Some plugins like
> pytest-capturelog
> > > > > > > have seen their latest release three years ago but remain
> > > functional.
> > > > > > > A good sign that the plugin system is reasonable i guess.
> > > > > > >
> > > > > > > If someone wants to help with organizing plugin compatibility
> > > > > > > tests and maintaining a status page, i'd really appreciate
> that.
> > > > > > > With over 50 existing plugins it's not easy to stay on top.
> > > > > > > The current pytest.org page is only a start:
> > > > > > >
> > > > > > >     http://pytest.org/latest/plugins.html#extplugins
> > > > > > >
> > > > > > > and here is the full pypi list:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> https://pypi.python.org/pypi?%3Aaction=search&term=pytest-&submit=search
> > > > > > >
> > > > > > > there are also some github/bitbucket-only plugins, in addition.
> > > > > > >
> > > > > > > And finally a note to plugin authors: please be subscribed
> > > > > > > to pytest-dev and post new plugin releases here.
> > > > > > >
> > > > > > > best,
> > > > > > > holger
> > > > > > >
> > > > > > > pytest-xdist-1.9:
> > > > > > >
> > > > > > > - changed LICENSE to MIT
> > > > > > >
> > > > > > > - fix duplicate reported test ids with --looponfailing
> > > > > > >   (thanks Jeremy Thurgood)
> > > > > > >
> > > > > > > - fix pytest issue41: re-run tests on all file changes, not
> just
> > > > > > >   randomly select ones like .py/.c.
> > > > > > >
> > > > > > > - fix pytest issue347: slaves running on top of Python3.2
> > > > > > >   will set PYTHONDONTWRITEYBTECODE to 1 to avoid import
> concurrency
> > > > > > >   bugs.
> > > > > > >
> > > > > > > pytest-xprocess-0.8:
> > > > > > >
> > > > > > > - support python3 (tested on linux/win32)
> > > > > > >
> > > > > > > - split out pytest independent process support into xprocess.py
> > > > > > >
> > > > > > > - add info.kill() method and some smaller refactoring
> > > > > > >
> > > > > > > - fix various windows related Popen / killing details
> > > > > > >
> > > > > > > - add tests
> > > > > > >
> > > > > > >
> > > > > > > pytest-pep8:
> > > > > > >
> > > > > > > - use pytest-2.4.2 node.add_marker() API for adding "pep8"
> marker
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Pytest-dev mailing list
> > > > > > > Pytest-dev at python.org
> > > > > > > https://mail.python.org/mailman/listinfo/pytest-dev
> > > > > > >
> > > > >
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20131009/4a7f4beb/attachment.html>