Skip to content

use consistent inner repressentation for marks#1923

Merged
flub merged 3 commits intopytest-dev:featuresfrom
RonnyPfannschmidt:mark-internal-value
Sep 19, 2016
Merged

use consistent inner repressentation for marks#1923
flub merged 3 commits intopytest-dev:featuresfrom
RonnyPfannschmidt:mark-internal-value

Conversation

@RonnyPfannschmidt
Copy link
Copy Markdown
Member

this pr makes the internals of markers a more consistent structure to use as a base for future enhancements

currently the new mark type is not exposed,
but it is a intent to remove usages of MarkInfo/MarkDecorator in favor of Mark objects and potentially collections/views over them later on

@RonnyPfannschmidt RonnyPfannschmidt added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label Sep 8, 2016
@coveralls
Copy link
Copy Markdown

coveralls commented Sep 8, 2016

Coverage Status

Coverage increased (+0.02%) to 93.093% when pulling 1812387 on RonnyPfannschmidt:mark-internal-value into 1c9bd92 on pytest-dev:features.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.02%) to 93.093% when pulling 4552424 on RonnyPfannschmidt:mark-internal-value into 1c9bd92 on pytest-dev:features.

Copy link
Copy Markdown
Member

@flub flub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Would be nice to avoid the internal mark API in the skipping plugin though.

Comment thread _pytest/skipping.py
else:
arglist = [(self.holder.args, self.holder.kwargs)]
for args, kwargs in arglist:
marks = getattr(self.holder, '_marks', None) \
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not that this is made worse by this PR but it's not nice that this uses an internal attribute of the MarkInfo. Should markinfo not make this public somehow instead? How about using the MarkInfo as an iterator? I think that gives you access to all args/kwargs individually.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@flub when i did this the first time (the pr we rejected at the sprint)

i did move this code into the marks module

i plan to fix it eventually, but that was not in the scope of this pr

@flub flub merged commit 01db0f1 into pytest-dev:features Sep 19, 2016
@RonnyPfannschmidt RonnyPfannschmidt deleted the mark-internal-value branch June 11, 2017 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants