Skip to content
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.

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

pytest_configure calling order #2539

Closed
Ignalion opened this issue Jun 30, 2017 · 5 comments
Closed

pytest_configure calling order #2539

Ignalion opened this issue Jun 30, 2017 · 5 comments

Comments

@Ignalion
Copy link

@Ignalion Ignalion commented Jun 30, 2017

Hi guys. Have a little question about order of calling different pytest_configure from conftest.py and plugins files.
Is there a documented or some unspoken order of calling this hook when it's present in different conftest.py files and\or plugins?

@RonnyPfannschmidt
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt commented Jun 30, 2017

for initial conftests and plugins the call order is random and affectable via tryfirst/trylast,

for other conftests it hapens right at loading time

we should document this indeed

@RonnyPfannschmidt
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt commented Jun 30, 2017

oh, and extra note - due to python3.6 dict ordering it ill happen in import order on python 3.6+ for now

@Ignalion
Copy link
Author

@Ignalion Ignalion commented Jun 30, 2017

Thus, as I understand, I can't rely on theirs order. Thanks!

@RonnyPfannschmidt
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt commented Jun 30, 2017

Reopened as we should document this one in the own docs

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented Jun 30, 2017

Perhaps @Ignalion would like to take a stab at contributing this? 😉

nicoddemus added a commit that referenced this issue Jul 4, 2017
Fix #2539
nicoddemus added a commit to nicoddemus/pytest that referenced this issue Jul 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants