Re: [pytest-dev] Shipping conftest.py in a python library

2016-09-05 Thread Zack Allen
Great! Thank you! On Mon, Sep 5, 2016 at 3:05 AM, Ronny Pfannschmidt wrote: > Hi Zach, > > the classical way to do that is to turn what is a conftest into a normal > python package > afterwards any project can put that into the pytest_plugins variable. > > also you could add a setuptools entrypo

Re: [pytest-dev] [proposal] deprecating the pytest_namespace hook

2016-09-05 Thread Florian Bruhin
* Floris Bruynooghe [2016-09-05 12:11:12 +0100]: > > > the second problem it creates is, it makes the pytest namespace > > > impossible to introspect for external tools > > > > > > I agree that's annoying, but that's a problem in general on how dynamic > > > pytest is (IDEs don't autocomp

Re: [pytest-dev] [proposal] deprecating the pytest_namespace hook

2016-09-05 Thread Floris Bruynooghe
On Fri, Aug 26, 2016 at 03:06:57PM +0200, Ronny Pfannschmidt wrote: > On 26.08.2016 15:00, Bruno Oliveira wrote: > > On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt > > > > wrote: > > > > the problem it creates is, that we need to load plugins before

Re: [pytest-dev] Shipping conftest.py in a python library

2016-09-05 Thread Ronny Pfannschmidt
Hi Zach, the classical way to do that is to turn what is a conftest into a normal python package afterwards any project can put that into the pytest_plugins variable. also you could add a setuptools entrypoint like the normal 3rd party pytest plugins use to enable it in all cases -- Ronny 2016-