Re:What's up, Python? The GIL removed, a new compiler, optpa...
by da39a3ee on Monday July 31, 2023 @09:09AM
(#36941984)
Is what you're describing only true of the "Framework" Python build on MacOS? It sounds like that's the case from a quick read of the issue you linked. I would say that people should basically never use the "Framework" Python on MacOS. (There's some insanity IIRC where matplotlib wants you to use the Framework build? But that's matplotlib)
[ Parent
| on HN ]
Re:What's up, Python? The GIL removed, a new compiler, optpa...
by zbentley on Monday July 31, 2023 @09:23AM
(#36942115)
> Is what you're describing only true of the "Framework" Python build on MacOS?
No. This behavior is present on any Python 3.8 or greater running on MacOS, enforced via "platform == darwin" runtime check: https://github.com/python/cpython/pull/13626/files#diff-6836...
You can check the default process-start method of your Python's multiprocessing by running this command: "python -c 'import multiprocessing; print(multiprocessing.get_start_method())'"