Skip to content

pytester: a couple of fixes for pytester.plugins in subprocess mode #13522

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

bluetech
Copy link
Member

Please see the commit messages.

This is just from looking at the code, didn't run into this personally. I think there is no reason to backport.

@bluetech bluetech force-pushed the pytester-subprocess-plugins branch from 64151cf to 3a094ee Compare June 16, 2025 08:25
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Jun 16, 2025
Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Agree we should not backport this.

bluetech added 3 commits June 16, 2025 20:36
…he first

As far as I can see, there is no reason for this, seems like a mistake.
…ead of silently ignoring

In subprocess mode, adding a non-str plugin object to `pytester.plugins`
can't work. Previously, such plugins would just be silently ignored.
Silently ignoring an explicit setup doesn't seem right. Error instead.
@bluetech bluetech force-pushed the pytester-subprocess-plugins branch from 3a094ee to 6669073 Compare June 16, 2025 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided (automation) changelog entry is part of PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants