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

2016-10-20 Thread Bruno Oliveira
On Thu, Oct 20, 2016 at 12:33 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: I'm still not getting how that fits with the collection of *tests*... consider this module: # contents of test_foo.py from pytest_blocker import Blocker @Blocker(123) def test_foo(): pass fist that

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

2016-10-20 Thread Ronny Pfannschmidt
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 names. I'm not entirely sure what this

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

2016-10-20 Thread Bruno Oliveira
Hey Ronny, On Thu, Oct 20, 2016 at 10:55 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > b) Another suggestion from Ronny: running collection and getting used > marker names. I'm not entirely sure what this means exactly, since the > original proposal doesn't use "names" at all

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

2016-10-20 Thread Ronny Pfannschmidt
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 trying to turn various internal mark

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

2016-10-20 Thread Bruno Oliveira
On Thu, Oct 20, 2016 at 7:12 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: On 20.10.2016 10:56, holger krekel wrote: > Hey Ronny, > > i >> while trying to turn various internal markers of a work project >> into public plugins, i noticed a very plain problems - different other >>

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

2016-10-20 Thread Ronny Pfannschmidt
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

2016-10-20 Thread holger krekel
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 the

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

2016-10-19 Thread Floris Bruynooghe
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 purposes/intents > > such a flat

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

2016-10-13 Thread Bruno Oliveira
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 to be the "recommended

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

2016-09-07 Thread Ronny Pfannschmidt
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 purposes/intents such a flat namespace really doesn't scale as such i would like to propose havin