Ned Deily <n...@python.org> added the comment:
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!
----------
resolution: -> third party
stage: -> resolved
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue38814>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
