Closed nathanjmcdougall closed 4 months ago
Ok, I was able to reproduce this error on Windows, and I was also able to reproduce on Linux after calling multiprocessing.set_start_method('spawn')
or multiprocessing.set_start_method('forkserver')
(Linux defaults to a start method of 'fork'
).
Unfortunately this is an inherent issue with those start methods so the only resolution here is to document it, which I've done here: https://github.com/ben-denham/labtech/commit/88265be51a60159fb4f64c3c7afc4921d941c7b5
When running the code at
tests\integration\readme\dependents_and_mermaid.py
by pasting lines into Powershell on Windows, I get this lengthly stack trace. As far as I can tell, it seems to be some issue with Pickling going wrong, but I haven't looked into the details at all. See output below.Note that this issue does not reproduce when running the
.py
file directly viapoetry run python tests\integration\readme\dependents_and_mermaid.py
, see https://github.com/ben-denham/labtech/issues/16#issuecomment-2119980702Maybe this is something to do with the way that
__name__
works, which is not something I have ever fully understood.