Skip to content

marks applied in parametrize are stored as markdecorator #2400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
RonnyPfannschmidt opened this issue May 11, 2017 · 3 comments
Closed

marks applied in parametrize are stored as markdecorator #2400

RonnyPfannschmidt opened this issue May 11, 2017 · 3 comments
Labels
topic: marks related to marks, either the general marks or builtin

Comments

@RonnyPfannschmidt
Copy link
Member

while parametrizing i found that things break appart due to the markers coming from the parameterization are stored as markdecorator instead of marks

this is also the final line for me wrt trying to keep marks backward compatible ^^

i plan to break them now in terms of internals to we can get something usable
@RonnyPfannschmidt RonnyPfannschmidt added the topic: marks related to marks, either the general marks or builtin label May 13, 2017
@RonnyPfannschmidt
Copy link
Member Author

this triggers #1540

@RonnyPfannschmidt
Copy link
Member Author

this was in part resolved by introducing pytest.param

@RonnyPfannschmidt
Copy link
Member Author

fixed in #3317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: marks related to marks, either the general marks or builtin
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RonnyPfannschmidt