Davin Potts added the comment:
The example demonstrating the issue is reproducible on Windows (tested on
Windows 7 64-bit, specifically) with 2.7.9. Complications arising from how
multiprocessing creates new processes on Windows combined with conventions in
the import system in 2.7.9 result
Éric Araujo mer...@netwok.org added the comment:
I’m not sure this belongs on the Python tracker.
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8534
___
Changes by Ask Solem a...@opera.com:
--
keywords: +needs review
nosy: +asksol
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8534
___
___
New submission from simon ext-simon.stei...@nokia.com:
testmultiprocessing.py:
def main():
import multiprocessing
proc = multiprocessing.Process(target=runhi)
proc.start()
proc.join()
def runhi():
print 'hi'
if __name__ == __main__:
main()
Changes by Antoine Pitrou pit...@free.fr:
--
assignee: - jnoller
nosy: +jnoller
priority: - low
stage: - needs patch
type: - behavior
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
Changes by simon ext-simon.stei...@nokia.com:
--
keywords: +patch
Added file: http://bugs.python.org/file17092/forking.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8534
___
