Hi Florian, I definitely agree with you about making it clear what users have to do to replace deprecated functionality, which brings to attention that we could improve the bit about markers in parametrize deprecation as it stands now in the CHANGELOG.
But the __multicall__ warning was not added to 3.2, it has been in place since 2015. Are you seeing this warning just now? Cheers, Bruno. On Fri, Jul 14, 2017 at 4:51 AM Florian Schulze <florian.schu...@gmx.net> wrote: > Works fine with devpi, but ... > > I got the __multicall__ deprecation warning and had a very hard time to > find information on how to actually fix it. In the end I found the PR that > changes the docs in pytest which allowed me to change our fixture. > > So, if you deprecate something, please provide easy to find docs on how to > actually fix it, even if the old stuff was undocumented. An example diff is > often enough. > > Regards, > Florian Schulze > > On 14 Jul 2017, at 0:45, Bruno Oliveira wrote: > > Hi everyone, > > I have prepared a package for the 3.2.0 release and it would be great if > people could help test it. > > The package is available at: > > https://devpi.net/nicoddemus/dev/pytest/3.2.0 > > And can be installed with: > > pip install -U > https://devpi.net/nicoddemus/dev/+f/aeb/edee851da9e58/pytest-3.2.0-py2.py3-none-any.whl > > If all goes well I plan to release it during the weekend. > > Cheers, > Bruno. > > _______________________________________________ > > > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
