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

problem with the multiprocessing module on windows with python3.9 #195

Open
djmoto24 opened this issue Jun 4, 2021 · 0 comments
Open

problem with the multiprocessing module on windows with python3.9 #195

djmoto24 opened this issue Jun 4, 2021 · 0 comments

Comments

@djmoto24
Copy link

djmoto24 commented Jun 4, 2021

pydev debugger: starting (pid: 4736)
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 116, in spawn_main
exitcode = _main(fd, parent_sentinel)
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 125, in _main
prepare(preparation_data)
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 236, in prepare
_fixup_main_from_path(data['init_main_from_path'])
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
main_content = runpy.run_path(main_path,
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 268, in run_path
return _run_module_code(code, init_globals, run_name,
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 97, in _run_module_code
_run_code(code, mod_globals, init_globals,
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\ladmin\eclipse-workspace\fabula\fabfile.py", line 15, in <module>
service=docker.Service(
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\site-packages\fabricio\docker\base.py", line 219, in __init__
self.managers = multiprocessing.Manager().dict()
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\context.py", line 57, in Manager
m.start()
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\managers.py", line 553, in start
self._process.start()
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\process.py", line 121, in start
self._popen = self._Popen(self)
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\context.py", line 327, in _Popen
return Popen(process_obj)
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\popen_spawn_win32.py", line 45, in __init__
prep_data = spawn.get_preparation_data(process_obj._name)
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 154, in get_preparation_data
_check_not_importing_main()
File "C:\Users\ladmin\AppData\Local\Programs\Python\Python39\lib\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.

The "freeze_support()" line can be omitted if the program
is not going to be frozen to produce an executable.**

@djmoto24 djmoto24 changed the title problem with the multiprocessing module on windows problem with the multiprocessing module on windows with python3.9 Jun 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant