Hi Ronny, everyone, i had actually replied to this mail a few days ago but it got lost due to my playing around with new mail setups and clients :/
So here is my 2cent collection IIRC: - IMO py is in low-effort maintenance mode. Removing anything is likely to break things, increase maintenance effort -> not worth it. - pylib could in tox.ini for testing just depend on pytest<3.0 and be done with it. That's probably good enough for the next 1-2 years. - meanwhile pytest can rather aim to vendor/get rid of things like we did with py.code. A big thing probably here is py.path.local usage. Maybe writing a wrapper around pathlib with py.path.local API would be a good not too cumbersome strategy because it doesn't touch much code. best, holger On Thu, Sep 22, 2016 at 14:15 +0200, Ronny Pfannschmidt 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
