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
Labels
good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic type: docs documentation improvement, missing or needing clarification

Comments

@Ignalion
Copy link

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

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 RonnyPfannschmidt added type: docs documentation improvement, missing or needing clarification good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic labels Jun 30, 2017
@RonnyPfannschmidt
Copy link
Member

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

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

@RonnyPfannschmidt
Copy link
Member

Reopened as we should document this one in the own docs

@nicoddemus
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

No branches or pull requests

3 participants