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 same generic marker name for different purposes/intents > > such a flat namespace really doesn't scale The more plugins there are the more it causes potential clashes of marker and fixture names. We've had some discussions at the sprint about it IIRC. I suggest that whatever namespacing we come up with it should be a) backward-compatible b) work for both markers and fixtures. > as such i would like to propose having marker types and objects as > importable objects > > > for example > > > > import pytest > from pytest_bugzilla import Blocker > > > @pytest.mark(Blocker(123)) > def test_fun(): > pass > > that way we can do both, reuse python name-spacing *and* use more > meaningful objects for markings a few questions: - How would you integrate this with interactive help such as "py.test --markers"? - how would you access the Blocker marker from a hook? New API? - how would you apply it at module or class level? holger _______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
