Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

On 20.10.2016 15:14, Bruno Oliveira wrote: > Hey Ronny, > > > On Thu, Oct 20, 2016 at 10:55 AM Ronny Pfannschmidt > > wrote: > >> b) Another suggestion from Ronny: running collection and getting >> used marker

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

HI Bruno On 20.10.2016 14:20, Bruno Oliveira wrote: > On Thu, Oct 20, 2016 at 7:12 AM Ronny Pfannschmidt > > wrote: > > > On 20.10.2016 10:56, holger krekel wrote: > > Hey Ronny, > > > > i > >> while

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

Hi Holger, On 20.10.2016 10:56, holger krekel wrote: > Hey Ronny, > > i'd like to get back to your original suggestion ... > > On Wed, Sep 07, 2016 at 11:38 +0200, Ronny Pfannschmidt wrote: >> Hi all, >> >> while trying to turn various internal markers of a work project >> into public plugins, i

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

Hey Ronny, i'd like to get back to your original suggestion ... On Wed, Sep 07, 2016 at 11:38 +0200, Ronny Pfannschmidt wrote: > Hi all, > > while trying to turn various internal markers of a work project > into public plugins, i noticed a very plain problems - different other > plugins used

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

On 7 September 2016 at 10:38, Ronny Pfannschmidt wrote: > Hi all, > > while trying to turn various internal markers of a work project > into public plugins, i noticed a very plain problems - different other > plugins used the same generic marker name for different

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

Hey Ronny, On Wed, Sep 7, 2016 at 10:45 AM Ronny Pfannschmidt wrote: > such a flat namespace really doesn't scale > > as such i would like to propose having marker types and objects as > importable objects > I'm not against adding support for it, but I wouldn't change it