[pytest-dev] the sorry state of pylib tests and pylib
nicoddemus at gmail.com
Tue Sep 27 08:51:58 EDT 2016
How long do we plan to maintain pylib? Perhaps we can get rid of stuff we
no longer wish to maintain (svn, py.code) and release a 2.0 version? If
someone still needs that functionality, they can pin it.
Not sure about the py.path encoding errors you mention though.
On Thu, Sep 22, 2016 at 9:16 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:
> 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
> c) depending on environment there are massive issues with pylib path
> as far as i can tell thats just scratching the surface
> im not yet sure what to do about it, but some thing has to be done ^^
> -- Ronny
> pytest-dev mailing list
> pytest-dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pytest-dev