[pytest-dev] re-running pytest on file changes

Hi, I'm trying to wrap my head around this subject. Is there a strong reason why the -f looponfail option is inside a plug-in? My hunch would be to do it as a separate, flexible, command, but that's just feelings without any experience. Poll: Do you guys use looponfail? Has it been working good?

Re: [pytest-dev] release checklist / de-monopolizing release process

On Thu, Mar 26, 2015 at 19:12 -0300, Bruno Oliveira wrote: > Hi, > > > If we assume that pytest-2.7.X will be "bugfix only" we could > > tie its doc target to "latest" and ask everybody who does doc enhancements > > to target their PRs to "latest". > > Seems reasonable to me, but what about doc fi