-
Notifications
You must be signed in to change notification settings - Fork 25
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
[WIP] Import pluggy directly #4
[WIP] Import pluggy directly #4
Conversation
I filed https://github.com/davehunt/pytest-metadata/issues/5 instead/in addition - please close/comment, etc. as necessary :-) |
@@ -5,7 +5,7 @@ | |||
import os | |||
import platform | |||
|
|||
import _pytest._pluggy as pluggy | |||
import pluggy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just going to make this change myself.
Maybe we should make it a conditional so that we don't break users of the plugin.
try:
import pluggy
except ImportError:
import _pytest._pluggy as pluggy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it should be the other way around, else it reports the wrong pytest pluggy version
for completeness it should probably report both, pytest pluggy and global pluggy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be like Ronny suggested.
try:
import _pytest._pluggy as pluggy
except ImportError:
import pluggy
Also it is probably worth to add more pytest versions to |
Fixed in davehunt@4d28adc. @nicoddemus should we move this plugin to pytest-dev? |
@davehunt sure thing! Do you have the necessary permissions I assume? |
I think only admins of pytest-dev can do that @nicoddemus. If I recall correctly when we moved my other plugins last year I transferred them to you, and you created the necessary teams according to https://docs.pytest.org/en/latest/contributing.html#submitplugin and transferred the repo to pytest-dev. |
Oh I see. @davehunt let's proceed according to protocol then? Could you please send an email to the mailing list requesting the move? I will reply right away agreeing and once another person agrees we can go forward with the move. 👍 |
Sorry, @davehunt - I haven't run this at all, and don't know the ramifications of this change, other than pytest has stopped vendoring pluggy as of 3.3.0 (see pytest-dev/pytest#2719). (Perhaps I should've just filed an Issue, instead.)