Python 为什么ubuntu和macOS中的多进程工作方式不同?

Python 为什么ubuntu和macOS中的多进程工作方式不同?,python,ubuntu,multiprocessing,macos-big-sur,Python,Ubuntu,Multiprocessing,Macos Big Sur,我有这个简单的代码使事情变得更简单 from multiprocessing import Process def abc(): print("HI") print(a) a = 4 p = Process(target = abc) p.start() 它在ubuntu(Python 3.8.5)中运行良好,并提供以下输出: HI 4 但是,它在spyder(Python3.9.5)“AttributeError:无法在”和macOS(Python3.

我有这个简单的代码使事情变得更简单

from multiprocessing import Process
def abc():
    print("HI")
    print(a)

a = 4
p = Process(target = abc)
p.start()
它在ubuntu(Python 3.8.5)中运行良好,并提供以下输出:

HI
4
但是,它在spyder(Python3.9.5)“AttributeError:无法在”和macOS(Python3.8.10,我也尝试了其他版本,但失败了)CLI“RuntimeError”中失败

Spyder错误:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "multiprocessing/spawn.pyc", line 116, in spawn_main
  File "multiprocessing/spawn.pyc", line 126, in _main
AttributeError: Can't get attribute 'abc' on <module '__main__' (built-in)>
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "multiprocessing/spawn.pyc", line 116, in spawn_main
  File "multiprocessing/spawn.pyc", line 126, in _main
AttributeError: Can't get attribute 'abc' on <module '__main__' (built-in)>
回溯(最近一次呼叫最后一次):
文件“”,第1行,在
文件“multiprocessing/spawn.pyc”,第116行,在spawn_main中
文件“multiprocessing/spawn.pyc”,第126行,在_main中
AttributeError:无法在上获取属性“abc”
回溯(最近一次呼叫最后一次):
文件“”,第1行,在
文件“multiprocessing/spawn.pyc”,第116行,在spawn_main中
文件“multiprocessing/spawn.pyc”,第126行,在_main中
AttributeError:无法在上获取属性“abc”
MacOS BigSur错误:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 125, in _main
    prepare(preparation_data)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 236, in prepare
    _fixup_main_from_path(data['init_main_from_path'])
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 287, in _fixup_main_from_path
    main_content = runpy.run_path(main_path,
  File "/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py", line 265, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/Users/asavas/delete.py", line 8, in <module>
    p.start()
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 42, in _launch
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 154, in get_preparation_data
    _check_not_importing_main()
  File "/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 134, in _check_not_importing_main
    raise RuntimeError('''
RuntimeError: 
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.
回溯(最近一次呼叫最后一次):
文件“”,第1行,在
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第116行,在spawn_main中
exitcode=_main(fd,父节点_sentinel)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第125行,在
准备(准备数据)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第236行,在prepare中
_从路径修复主路径(数据['init\u main\u from\u path'])
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第287行,位于\u fixup\u main\u from\u路径中
main\u content=runpy.run\u路径(main\u路径,
文件“/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py”,第265行,在运行路径中
返回运行模块代码(代码、初始化全局、运行名称、,
文件“/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py”,运行模块代码第97行
_运行代码(代码、mod_globals、init_globals、,
文件“/Users/asavas/opt/anaconda3/lib/python3.8/runpy.py”,运行代码第87行
exec(代码、运行\全局)
文件“/Users/asavas/delete.py”,第8行,在
p、 开始()
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/process.py”,第121行,开始
self.\u popen=self.\u popen(self)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/context.py”,第224行,在
返回_default_context.get_context().Process._Popen(Process_obj)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/context.py”,第284行,在
返回Popen(过程对象)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py”,第32行,在__
super().\uuuu init\uuuj(进程对象)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_fork.py”,第19行,在__
自启动(过程obj)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py”,第42行,在发布中
prep_data=spawn.get_preparation_data(进程对象名称)
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第154行,在get_准备_数据中
_选中\u not \u导入\u main()
文件“/Users/asavas/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py”,第134行,在“检查”非“导入”主目录中
引发运行时错误(“”)
运行时错误:
已尝试在启动之前启动新进程
当前进程已完成其引导阶段。
这可能意味着您没有使用fork启动您的应用程序
子进程,而您忘记了使用正确的习惯用法
在主模块中:
如果uuuu name uuuuuu='\uuuuuuu main\uuuuuuu':
冻结支持()
...
如果程序
不会冻结以生成可执行文件。
试图了解我为什么以及如何解决此问题


感谢

看来,此版本的macOS已切换到使用
spawn
而不是
fork
方法来创建新进程。这意味着当创建新进程时,将创建一个新的空地址空间,启动一个新的Python解释器,并从顶部重新执行源文件。consequence通常,任何位于全局作用域且不在以
开头的块中的代码(如果uuu name_uuu=='uuu main_uuu':
将被执行。这就是为什么创建进程的任何代码都必须位于这样的块中,否则将进入递归的进程创建循环,从而生成所看到的错误。您只需要:

来自多处理导入进程的

def abc():
打印(“HI”)
印刷品(a)
#这将在新的子流程中重新执行:
a=4
如果uuuu name uuuuuu='\uuuuuuu main\uuuuuuu':
p=过程(目标=abc)
p、 开始()
p、 join()#显式等待进程完成

“CLI
运行时错误
”-错误消息是怎么说的?我认为这是一个重复的问题,但这个问题涉及到
。如果我在Ubuntu中使用python 3.8.5和python 3.9.5,但在MacOS上,python 3.9.0给出了erorr消息
在当前进程完成引导阶段之前尝试启动一个新进程。
刚刚添加了完整的错误消息您是否阅读了完整的错误消息,然后相应地调整了代码,即如果_uname_uuu==“_uumain_uu”,则将主代码包装在
idiom?这在MacOS上很管用,但在Spyder中,如果我执行我想应该执行的代码,仍然会收到错误消息,但如果我运行文件,则不会得到打印输出。请看一看。也许它解决了您的问题。“Spawn”是MacOS上python 3.8+上的默认启动方法,以前默认为“fork”。其他*nix系统仍默认为“fork”,windows继续只提供“spawn”(从2021年初开始)。可能是您有多个python安装,spyder使用的是较旧或较新的版本。