sassoftware / sassoftware/python-swat

Not working well with multiprocessing library fork start method

Open
#107 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
159
Forks
65
PR merge metrics
No merged PRs in 30d

Description

Hi, when I use multiprocessing library on Unix machine, the CAS connection cannot return or print out my evaluated table to my disk, whether I use to_csv() or to_pickle().

However, if I change the start mode to Windows default spawn mode, it will work without issue. multiprocessing.set_start_method('spawn')

Please refer to this link for more information.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue on a Unix machine with multiprocessing's fork start method and a CAS connection, then compare it with the documented spawn workaround. Check whether evaluated tables can be written with to_csv() and to_pickle(); done means both operations return or print the table to disk under fork.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.