[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Ronald Oussoren added the comment: The installers on Python.org no longer use the system version of libsqlite, sidestepping that issue. That doesn't fix the issue with _scproxy, but that's something we cannot easily fix in Python itself. -- resolution: -> wont fix stage: -> resol

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Change by Eitan Adler : -- nosy: +eadler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Chris Jerdonek added the comment: > We can't solve that problem; only Apple can; > So, if we don't change _scproxy or urllib*'s use of it, only Apple can fix > the problem. In the Django ticket I mentioned in my comment above, one of the commenters said, "Just ran the tests at the mentioned c

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Chris Jerdonek added the comment: FWIW, I just came across an issue in Django's test suite that I believe is caused by the issue reported here. Some of Django's unit tests were hanging for me when run in "parallel" mode (which uses multiprocessing). Here is the ticket I filed there: https://co

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Changes by Chris Jerdonek : -- nosy: +chris.jerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Evan Jones added the comment: I have a crazy idea, but I'm not 100% sure how to implement it: If Python was able to detect and report this error in a friendly way, it would allow people to easily understand what is happening and to work around it. How can we do it? First idea: In the implement

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Ronald Oussoren added the comment: There is a clear gap between two use cases for Python on OSX: 1) Integrate nicely with Apple stuff 2) Be useful as a development platform for software that will be deployed on Linux machines. Both use cases are valid, but have slightly different trade-offs.

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Evan Jones added the comment: To be clear: My reproduction scripts crash both Python 2.7.10 and Python 3.5.1 when you: 1. Download the source bundle from python.org. 2. Run ./configure; make 3. Use the built binary (because ./configure picks up the system version of libsqlite.dylib) I did som

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Ned Deily added the comment: Thanks for your analysis! I'm sure that you are correct about Issue20353. It could also be the root cause of other crashes reported when internet proxies are used with urllib* invoking the _scproxy helper extension module, as reported in Issue13829. The question