This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients karolyi, ned.deily, ronaldoussoren
Date 2019-11-16.05:36:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573882581.76.0.461131786657.issue38814@roundup.psfhosted.org>
In-reply-to
Content
Sorry but with a non-debug build of Python, it's not very likely someone would  be able to glean much from the macOS crash stack trace here.  You also seem to have a very large number of C extension modules, some apparently from Homebrew and others from other sources ("/Users/USER/*/" ?). Also, I don't understand what you mean by:

"I use homebrew with the latest packages and python3.7.5 is now compiled from source, to avoid dependency problems."

And it seems you were reporting lots of problems on IRC beyond what is reported here.

The best I can suggest is to try to ensure that all binaries you are using are all from one source, for example, Homebrew or conda, and make sure any packages with C extension modules are built using the same python instance.  If the problem persists, you may need to consider installing a debug version of Python or building one from source (./configure --with-pydebug ... ) but for 3.7.x at least that means you will also need to rebuild all packages that have C extension modules as debug mode has a different ABI.

Please feel free to reopen this issue with a reproducible test case if further investigation suggests a problem with Python itself.  Good luck!
History
Date User Action Args
2019-11-16 05:36:21ned.deilysetrecipients: + ned.deily, ronaldoussoren, karolyi
2019-11-16 05:36:21ned.deilysetmessageid: <1573882581.76.0.461131786657.issue38814@roundup.psfhosted.org>
2019-11-16 05:36:21ned.deilylinkissue38814 messages
2019-11-16 05:36:21ned.deilycreate