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
On 22.09.2016 12:27, Florian Schulze wrote:
> 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 from in test warnings (the
> thing pytest-warnings does atm but doesn't separate).
> Florian Schulze
> On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:
> im not aware of anyone signing up for that
> as far as i remember there also was no further development on the
> plugin itself
> -- Ronny
> On 21.09.2016 18:46, Bruno Oliveira wrote:
>> Hi everyone,
>> During the sprint Florian Schulze developed pytest-warnings,
>> and later we decided to merge that into pytest 3.1.
>> I was trying to remember: did anybody volunteer to do that?
>>  https://github.com/fschulze/pytest-warnings
>> pytest-dev mailing list
> pytest-dev mailing list
pytest-dev mailing list