Hi Ronny, 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. Cheers, On Thu, Sep 22, 2016 at 9:16 AM Ronny Pfannschmidt < [email protected]> 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 > it?) > > c) depending on environment there are massive issues with pylib path > encodings > > 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 > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
