Hi Bruno, On Wed, Nov 06, 2013 at 17:22 -0200, Bruno Oliveira wrote: > Hi Holger, all, > > Back from vacation, so I'm back to this. :) > > On Wed, Oct 30, 2013 at 8:42 AM, holger krekel <[email protected]> wrote: > > > > I just did devpi-*-1.2 releases. If you install devpi-client>=1.2 > > you get "devpi test --fallback-ini someini". Hope it helps. > > > > Works great, thanks. I'm keeping a branch "devpi" on pytest-plugs for this. > You can see one of the build results here: > > https://travis-ci.org/nicoddemus/pytest-plugs/builds/13596968 > > It basically installs a devpi server using "quickstart" and issues a series > of "devpi test" commands. Neat. > > One question: > > 1) Is there any way to overwrite the pytest version to use for running > "devpi test"? This is required if we want to test against different pytest > versions.
From "devpi test" there is no way currently other than passing in a custom tox.ini. We could think about adding an option to tox but it is not clear how that would look like. Maybe we could assume that the tox.ini that is being used has certain environments that would pin a pytest version. It is then a matter of reading out the "toxresults" that are posted to devpi after the tests have run. (you also see the result of reading that out from "devpi list X". There is no API documentation how to read it out but the code doing it is contained in devpi_client/list_remove.py (it's basically performing some http json requests). Our own "--fallback-ini" could of course pin pytest versions as well. best, holger > Cheers, > Bruno. > > > > best, > > holger > >
signature.asc
Description: Digital signature
_______________________________________________ Pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
