Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Florian Schulze
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 e

Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Bruno Oliveira
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

Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Florian Schulze
On 14 Jul 2017, at 14:04, Bruno Oliveira wrote: But the __multicall__ warning was not added to 3.2, it has been in place since 2015. Are you seeing this warning just now? I saw more warnings in general. Not sure if I tried before with a pytest that included pytest-warnings, but I think I tri

Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Oliver Bestwalter
Hi Bruno, I tried to install it into an existing Python 3.6 virtualenv and it stumbled over setuptools - running it again in the same env worked then. I pasted the call and a pip freeze here in case it is of interest: https://pastebin.com/xW7KfuuN Besides from that it works fine with the projects

Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Bruno Oliveira
On Fri, Jul 14, 2017 at 10:02 AM Florian Schulze wrote: > On 14 Jul 2017, at 14:04, Bruno Oliveira wrote: > > > But the __multicall__ warning was not added to 3.2, it has been in > > place > > since 2015. Are you seeing this warning just now? > > I saw more warnings in general. Not sure if I trie

Re: [pytest-dev] Help testing 3.2.0 release

2017-07-14 Thread Bruno Oliveira
On Fri, Jul 14, 2017 at 10:34 AM Oliver Bestwalter wrote: > Hi Bruno, > > I tried to install it into an existing Python 3.6 virtualenv and it > stumbled over setuptools - running it again in the same env worked then. I > pasted the call and a pip freeze here in case it is of interest: > https://p