Skip to content

Conversation

@goodboy
Copy link
Contributor

@goodboy goodboy commented Nov 18, 2017

This fixes #99 as well as removes any direct references to _HookCaller inside of the multi call loops.
This makes the call loops fully self contained without requiring any knowledge of overlying abstractions.

Tyler Goodlet added 3 commits November 13, 2017 16:36
Triggers a regression introduced during refactoring of the multicall
loop. Demonstrates the issue described in pytest-dev#99.
Multi-call loop(s) should not care about spec opts - only whether
or not the first result should be returned.
Fix issue where a collected but unmarked hook not having
`_HookCaller.spec_opts` defined results in an attr error.

Resolves pytest-dev#99
@goodboy goodboy changed the title Expose spec opts regresion Self contained call loops Nov 18, 2017
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt left a comment

Choose a reason for hiding this comment

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

nicely found, good work 👍

self._wrappers = []
self._nonwrappers = []
self._hookexec = hook_execute
self._specmodule_or_class = None
Copy link
Member

Choose a reason for hiding this comment

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

good unification 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Project name based collection triggers regression

2 participants