Hi!
I didn't/don't have time at the moment. But besides a minor issue there
isn't anything to do on the plugin.
In pytest itself we would have to replace the function calls with using
the warnings module and gather those. We likely want to present pytest
internal deprecations differently
Hi Florian,
thanks for the update.
im currently not too familiar with the internals myself
it seems like it will be slightly tricky to get right right,
as such i'd like to defer to 3.2 than end up in trouble right now
-- Ronny
On 22.09.2016 12:27, Florian Schulze wrote:
> Hi!
> I didn't/don't
Hi everyone,
while fixing up some pylib tests i noticed a set of massive issues
a) all py.code related tests are completely broken on pytest 3.0
b) the svn related tests are completely broken and outdated (can we kill
it?)
c) depending on environment there are massive issues with pylib path
