* Ronny Pfannschmidt <opensou...@ronnypfannschmidt.de> [2016-10-20 09:07:47
+0200]:
> > Finally, and I only just remembered, Holger has some lingering code
> > somewhere which does something like:
> >
> > @pytest.marker
> > def blocker(n):
> > return {'issue no': int(n)} # or whatever object you want your marker
> > to be
> >
> > @pytest.mark.blocker(123)
> > def test_fun():
> > pass
> fixtures and markers are not symmetric and i don't see a reason to make
> them be
> just for looking similar, currently they are *completely* different ,
> and i think that bringing them closer to look more nice will make things
> MUCH worse.
> they are belonging to different categories of "things" with completely
> different desired behaviours.Then don't think of them like fixtures - but markers are essentially *functions*. They have arguments and keyword arguments, and currently everything defining a marker with arguments has to do the parsing/validating by itself. Holger's proposal seemed to clean this up and make things a lot easier. Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
