[issue13829] exception error in _scproxy.so when called after fork

2016-08-06 Thread Evan Jones
Evan Jones added the comment: This is effectively the same as issue 27126. The discussion there convinced me that this may not be working around, since it isn't the only place this can happen! This same crash, caused by libdispatch not being fork compatible, also happens with sqlite and tk

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

2016-05-27 Thread Evan Jones
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

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

2016-05-26 Thread Evan Jones
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

[issue24573] Using multiprocessing with tkinter frames in Python 3.4.3 crashes in OS X

2016-05-25 Thread Evan Jones
Evan Jones added the comment: This is another instance of the following bug: http://bugs.python.org/issue27126 libdispatch (grand central dispatch) is not fork safe. The forkserver approach is a good workaround, thanks! -- nosy: +evan.jo...@bluecore.com

[issue27126] Mac system sqlite3 not fork safe: Bundle a version?

2016-05-25 Thread Evan Jones
Changes by Evan Jones <evan.jo...@bluecore.com>: Added file: http://bugs.python.org/file43004/osx_python3_crash.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue27126] Mac system sqlite3 not fork safe: Bundle a version?

2016-05-25 Thread Evan Jones
New submission from Evan Jones: The system version of libsqlite3 that is included in Mac OS X is not fork safe. This means that if a process forks, and the child calls into it, it will crash with the stack trace below. I've reproduced this with both Python 2.7.10 and Python 3.5.1 on Mac OS X

[issue20353] Hanging bug with multiprocessing + sqlite3 + tkinter (OS X 10.9 only)

2016-05-25 Thread Evan Jones
Evan Jones added the comment: I believe the root cause of this bug is the following issue: http://bugs.python.org/issue27126 ; a workaround is to run the following code before forking any subprocesses: sqlite3.connect(':memory:').close() -- nosy: +evan.jo...@bluecore.com

[issue1043134] Add preferred extensions for MIME types

2012-10-10 Thread Evan Jones
Changes by Evan Jones e...@evanjones.ca: -- nosy: +evanj ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1043134 ___ ___ Python-bugs-list mailing

[issue4696] email module does not unfold headers

2012-10-10 Thread Evan Jones
Changes by Evan Jones e...@evanjones.ca: -- nosy: +evanj ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4696 ___ ___ Python-bugs-list mailing list

[issue6123] tarfile:

2009-05-27 Thread Evan Jones
New submission from Evan Jones ev...@mit.edu: tarfile.open() with an empty tar archive fails with a ReadError exception. GNU tar refuses to create empty archives, but tarfile allows it. See the following code which reproduces the error. I used the version of tarfile.py from subversion (revision

[issue6123] tarfile: opening an empty tar file fails

2009-05-27 Thread Evan Jones
Changes by Evan Jones ev...@mit.edu: -- title: tarfile: - tarfile: opening an empty tar file fails ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6123