[pytest-dev] plugin status page

Bruno Oliveira nicoddemus at gmail.com
Wed Nov 13 15:30:47 CET 2013


Hi Holger,

I think we should allow instructing tox to override
> a version for a dependency.  Something like
>
>     tox --force-dep-version=pytest==2.4.2
>
> This would make tox replace any "pytest" dependency that is specified
> with tox itself.  It would not work for implicit dependencies
> specified within a setup.py's install_requires setting.  I guess
> we should extend the result-json format to include a list of all
> packages and dependencies for each environment so that we can do
> a double-check after tests were run.
>

I agree, that seems cleaner. I will take a look at tox in order to open a
PR for that.


> > In any case, it would be useful to everyone (plugin authors, users,
> > > pytest core devs) to see what is actually breaking (or working), i.e.
> > > the actual test failure/success log.  Is that available somewhere
> already?
> > >
> >
> > Hmm good point. It is available from the travis-ci output log, but that
> is
> > not very friendly. I will change the travis-ci jobs to also post the
> > results from "tox --result-json" which contains all the details from that
> > test session, and make that available from the webpage as well.
> >
> > So I'm thinking this should be the next steps:
> >
> > 1. Update plugins index page to include the status images;
> > 2. Post test results to the pytest-plugs page and make it available from
> > there;
> > 3. Find a nice way to ensure we are running "tox" with the pytest version
> > we want;
>
> makes sense.
>
> > About 3), I just had an idea... what if we install a devpi server that
> > would serve only the pytest version we want (say, 2.3.5) and force tox to
> > use that devpi server by using the "-i" option? Would that be possible?
> > ("Shadowed Release Files" seems to be what would be required for this to
> > work).
>
> See my suggestion above.  I think it would be more effort to do it
> indirectly via devpi-server here.
>

OK, let's see how that goes. :)

Cheers,
Bruno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20131113/cda8159f/attachment.html>


More information about the Pytest-dev mailing list