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

[WIP] Import pluggy directly #4

Closed

Conversation

stephendonner
Copy link

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.)

@stephendonner
Copy link
Author

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
Copy link

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

Copy link
Member

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

Copy link

@jayant2014 jayant2014 left a 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

@nicoddemus
Copy link
Member

Also it is probably worth to add more pytest versions to tox.ini.

@davehunt
Copy link
Collaborator

Fixed in davehunt@4d28adc. @nicoddemus should we move this plugin to pytest-dev?

@davehunt davehunt closed this Nov 28, 2017
@nicoddemus
Copy link
Member

@nicoddemus should we move this plugin to pytest-dev?

@davehunt sure thing! Do you have the necessary permissions I assume?

@davehunt
Copy link
Collaborator

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.

@nicoddemus
Copy link
Member

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. 👍

@stephendonner stephendonner deleted the pluggy-import-change branch November 28, 2017 18:05
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.

6 participants