Title: test_multiprocessing skipped on Windows
Type: behavior Stage: resolved
Components: Library (Lib), Windows Versions: Python 3.1, Python 3.2
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: brian.curtin Nosy List: brian.curtin, jnoller
Priority: high Keywords: patch

Created on 2010-08-04 15:41 by brian.curtin, last changed 2010-08-04 16:23 by brian.curtin. This issue is now closed.

File name Uploaded Description Edit
test_mp.diff brian.curtin, 2010-08-04 15:41 py3k
Messages (3)
msg112822 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-08-04 15:41
I just realized test_multiprocessing is being skipped on Windows because a few relative imports of _multiprocessing are failing in win32 specific code blocks. Attached is a trivial patch to remove the relative import, enabling the tests to run and succeed on both dev and installed environments.

Jesse: There don't appear to be any side effects here, but I get the feeling I might be overlooking some reason this might have been done.
msg112823 - (view) Author: Jesse Noller (jnoller) * (Python committer) Date: 2010-08-04 15:45
The relative imports have been more of a pain then they've helped. I'm fine with nuking them so long as the test suite passes.
msg112831 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-08-04 16:23
Fixed in r83722 (py3k) and r837274 (release31-maint).
Date User Action Args
2010-08-04 16:23:35brian.curtinsetstatus: open -> closed
versions: - Python 2.7
messages: + msg112831

resolution: fixed
stage: patch review -> resolved
2010-08-04 15:45:10jnollersetmessages: + msg112823
2010-08-04 15:41:14brian.curtincreate