Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Bruno Oliveira
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

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Ronny Pfannschmidt
HI Bruno, as things stand we have to maintain it until py.test no longer depends on it a 2.0 release that kills py.code is a non-option as any project dependign on ot will be limited in py.test version my plan is to de-vendor bits of pylib (like iniconfig, apipkg) some have been lone projects a

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Bruno Oliveira
On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt < [email protected]> wrote: > as things stand we have to maintain it until py.test no longer depends on > it > > a 2.0 release that kills py.code is a non-option as any project dependign > on ot will be limited in py.test version >

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Ronny Pfannschmidt
On 27.09.2016 15:59, Bruno Oliveira wrote: > On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt > > wrote: > > as things stand we have to maintain it until py.test no longer > depends on it > > a 2.0 release that kills py.code is a non-option

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Bruno Oliveira
On Tue, Sep 27, 2016 at 11:14 AM Ronny Pfannschmidt < [email protected]> wrote: > > > On 27.09.2016 15:59, Bruno Oliveira wrote: > > On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt < > [email protected]> wrote: > >> as things stand we have to maintain it until py.te

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Ronny Pfannschmidt
On 27.09.2016 16:25, Bruno Oliveira wrote: > > > On Tue, Sep 27, 2016 at 11:14 AM Ronny Pfannschmidt > > wrote: > > > > On 27.09.2016 15:59, Bruno Oliveira wrote: >> On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt >> >

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Florian Bruhin
* Bruno Oliveira [2016-09-27 14:25:43 +]: > Yes, but those downstream projects would have the option o pinning to pylib > < 2. Plus I think there must be almost no projects using it, it seems very > pytest specific, that was one of the reasonings we used to justify > vendoring py.code into pyt

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Ronny Pfannschmidt
Various distros debundle already, at least apipkg is severely outdated and a mess -- Ronny Am 27. September 2016 18:07:56 MESZ, schrieb Florian Bruhin : >* Bruno Oliveira [2016-09-27 14:25:43 +]: >> Yes, but those downstream projects would have the option o pinning to >pylib >> < 2. Plus I

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread holger krekel
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 maintenan

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread holger krekel
On Tue, Sep 27, 2016 at 18:07 +0200, Florian Bruhin wrote: > * Bruno Oliveira [2016-09-27 14:25:43 +]: > > Yes, but those downstream projects would have the option o pinning to pylib > > < 2. Plus I think there must be almost no projects using it, it seems very > > pytest specific, that was on

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Florian Bruhin
* holger krekel [2016-09-27 18:30:35 +0200]: > On Tue, Sep 27, 2016 at 18:07 +0200, Florian Bruhin wrote: > > * Bruno Oliveira [2016-09-27 14:25:43 +]: > > > Yes, but those downstream projects would have the option o pinning to > > > pylib > > > < 2. Plus I think there must be almost no proj

Re: [pytest-dev] the sorry state of pylib tests and pylib

2016-09-27 Thread Ronny Pfannschmidt
Hi Holger, over the course of the next few months i'd like to run the following actions on pylib 1. de-vendor apipkg - the version last released has bugfixes and works in bpython (low efford) 2. de-vendor iniconfig - that allows to get rid of the pylib dependency more easily (i already did a rele