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

-p no:plugin not working #2920

Closed
rpuntaie opened this issue Nov 13, 2017 · 3 comments
Closed

-p no:plugin not working #2920

rpuntaie opened this issue Nov 13, 2017 · 3 comments
Labels
topic: config related to config handling, argument parsing and config file type: bug problem that needs to be addressed

Comments

@rpuntaie
Copy link

OS: Windows 10
Python 3.6
Py.test 3.2.3

From the sources of pytest:

       group._addoption('-p', action="append", dest="plugins", default=[],
                 metavar="name",
                 help="early-load given plugin (multi-allowed). "
                 "To avoid loading of plugins, use the `no:` prefix, e.g. "
                 "`no:doctest`.")

My conftest.py is

      pytest_plugins = "integration"

But

      py.test test.py -p no:integration

does still include integration, which is in the same folder.

If I remove conftest.py, then integration is not included.
I would like to keep conftest.py and still by able to NOT include integration via command line.

Do I do something wrong or is this a bug?

@RonnyPfannschmidt RonnyPfannschmidt added topic: config related to config handling, argument parsing and config file type: bug problem that needs to be addressed labels Nov 13, 2017
@RonnyPfannschmidt
Copy link
Member

off hand this seems to be an issue with early initialization, unfortunately i wont be able to investigate soon

rpuntaie pushed a commit to rpuntaie/pytest that referenced this issue Nov 28, 2017
rpuntaie pushed a commit to rpuntaie/pytest that referenced this issue Nov 28, 2017
rpuntaie pushed a commit to rpuntaie/pytest that referenced this issue Nov 28, 2017
The-Compiler added a commit that referenced this issue Nov 29, 2017
@Sup3rGeo
Copy link
Member

Should this be closed as solved by #2964?

@nicoddemus
Copy link
Member

Yes, thanks @Sup3rGeo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: config related to config handling, argument parsing and config file type: bug problem that needs to be addressed
Projects
None yet
Development

No branches or pull requests

4 participants