-
Notifications
You must be signed in to change notification settings - Fork 667
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
Relax pluggy version dependency #3239
Conversation
The pluggy module was added back in 2019 - there are newer releases now, and we can expect other projects to depend on the 1.0 one - it would then conflict with molecule, preventing developers to run smoothly there unit tests.
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.
Correct fix is to make it < 2.0 as we already know that 1.0 did not break it and we do not expect any 1.x version to break it. It would be a more future proof dependency.
Oh, Thanks Sorin! I should have pinged you earlier :). |
Co-authored-by: Sorin Sbarnea <sorin.sbarnea@gmail.com>
Backport to stable/3.4: 💚 backport PR created✅ Backport PR branch: Backported as #3256 🤖 @patchback |
Co-authored-by: Sorin Sbarnea <sorin.sbarnea@gmail.com> (cherry picked from commit 212b01c)
Co-authored-by: Sorin Sbarnea <sorin.sbarnea@gmail.com> (cherry picked from commit 212b01c)
The pluggy module was added back in 2019 - there are newer releases now,
and we can expect other projects to depend on the 1.0 one - it would
then conflict with molecule, preventing developers to run smoothly there
unit tests.
PR Type