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
popen2 on Windows does not check _fdopen return value #39875
Comments
WinPython 2.3.3 crashes when using popen2 to spawn Running the test case on either W2k or Wxp causes I've no idea what system resource is being exhausted If you look at the hacks in posixmodule.c, the Python I'm sure there is a better way to eliminate the cmd.exe In any case, it appears we have an NT kernel bug As for *why* I'm doing this, it's because we're using The attached zip contains a test case, the posixmodule cheers,
|
The code for the popen* functions doesn't check the return |
Modules/posixmodule.c:_PyPopen() needs to check for NULL after the |
An easy C task for the bug day. |
Can this be closed as popen2 is deprecated? |
I think so. |
In particular, the popen2 entry says " "Deprecated since version 2.6: This module is obsolete. Use the subprocess module. Check especially the Replacing Older Functions with the subprocess Module section." On core-mentorship list, Guido answered 'Sure'. [close it] Let's hope that subprocess does better. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: