medium
shinokada opened this issue · comments
I use Python 3.7.7.
When I run
from retrieval import process_in_parallel, get_table_rows
table_rows = get_table_rows(fname='stats.html')
df = process_in_parallel(table_rows=table_rows, processes=25)
df.head()
It returns these errors.
objc[14401]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[14401]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[14411]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[14411]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[14412]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[14412]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
...
objc[14405]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[14405]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Do you know anything about how to fix these errors?