On Sun, Mar 26, 2017 at 06:29:04PM +0300, Frederick Muriithi wrote:
> I don't really see a reason why not. I have to point out though, that when
> writing the definition, I found python-pytest-2.9.2 also defined, with a
> note that it's there until all packages can be upgraded to use a more
> recent pytest.
> 
> Since I don't know what the progress on that is, I decided to err on the
> side of caution, and just add it with a note on why it's needed.

I added pytest 2.9.2 when I realized that many packages are picky about
which version of pytest they can use.

I checked, and all the packages that are using pytest 2.9.2 can use
pytest 3.0.7 instead.

So, here's a patch that updates the newer pytest across the board. It
goes after your patch series, unless you want to rebase your patches on
to it.

Soon we'll do a "python-updates" branch where we try to default to the
newer pytest, and keep an older one around for the outliers.