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

Optionally poison modules known to not work with pyfakefs #1089

Open
gsnedders opened this issue Nov 7, 2024 · 1 comment
Open

Optionally poison modules known to not work with pyfakefs #1089

gsnedders opened this issue Nov 7, 2024 · 1 comment

Comments

@gsnedders
Copy link

Is your feature request related to a problem? Please describe.
https://github.com/pytest-dev/pyfakefs/blob/main/docs/troubleshooting.rst#modules-not-working-with-pyfakefs documents a number of modules, most obviously multiprocessing and subprocess, as not playing nice with pyfakefs.

Describe the solution you'd like
I'd like to have a way for tests that call into functions in these modules to raise an exception (or at least raise a warning).

Describe alternatives you've considered
Trying to track down failures based on when pyfakefs does fail (often long after the call into problematic code in those modules).

@mrbean-bremen
Copy link
Member

Thanks, this may be a good idea! I have to check how feasible this is (also performance-wise), but I can give it a go. I see that as an add-in feature, and probably configurable regarding the excluded modules.
Not sure when I will get to it though (first have to tackle a couple of bugs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants