Hi,
On Sat, Feb 21, 2015 at 8:01 PM, holger krekel wrote:
> As far as pytest and tox are concerned i suggest (if anything) to reduce
> usage and dependency on pylib to the point where it can be removed as a
> dependency. This way there is no breaking combination of py/pytest
> ever. One area
Hi Bruno,
On Sat, Feb 21, 2015 at 17:32 -0200, Bruno Oliveira wrote:
> Hi Holger,
>
> On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote:
> >
> >
> > As far as pytest and tox are concerned i suggest (if anything) to reduce
> > usage and dependency on pylib to the point where it can be removed
Hi Bruno,
nope, it'll remain a separate lib, plans will made after py.test-2.7
-- Ronny
On Saturday, February 21, 2015 8:32:14 PM CEST, Bruno Oliveira wrote:
Hi Holger,
On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote:
As far as pytest and tox are concerned i suggest (if anything) to re
Hi Holger,
On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote:
>
>
> As far as pytest and tox are concerned i suggest (if anything) to reduce
> usage and dependency on pylib to the point where it can be removed as a
> dependency. This way there is no breaking combination of py/pytest
> ever.
Hi Ronny,
On Sat, Feb 21, 2015 at 19:46 +0100, Ronny Pfannschmidt wrote:
> Hi all,
>
> i'd like to start some very rough planing for pylib 2.0
> hoping for some comments
>
> main going a bit far things i currently have in mind
>
> * kill py.std
> * kill most of terminalwriter
> * move code/capt
Hi all,
i'd like to start some very rough planing for pylib 2.0
hoping for some comments
main going a bit far things i currently have in mind
* kill py.std
* kill most of terminalwriter
* move code/capture/saferepr to pytest ?
* kill svn path (its broken and nobody fixes it)
* de-vendorize a
