Ned Deily <n...@python.org> added the comment:
I'm sorry you are seeing that crash but I'm afraid it is difficult to know exactly what is going here without more information. It appears you are using a Python 3.7.7 from Homebrew along with NumPy and other similar third-party packages from somewhere. The macOS crash trace indicates that the crash occurred within the system dynamic loader, dyld, while apparently being called to find a function pointer for Python's import machinery (in _PyImport_FindSharedFuncptr) to dynamically link to. But with a standard non-debug build of Python, it's not really possible to figure out what was being called and exactly why. Without a reproducible test case, there is nothing much more we can do and, even so, it's pretty unlikely to be a problem in Python itself, more likely some combination of incompatibly-built C or C++ extension modules, environment variable, etc. Also, without knowing any context here, e.g. was this something that worked before you did some upgrade, etc, it makes it even harde r for anyone to speculate. If you can provide a simple test case, starting with how you installed everything and the exact steps to reproduce, somebody here *might* be able to give a better hint but you will likely get better help if you submit all that information to another forum that specializes in macOS NumPy, if nowhere else, StackOverflow. Good luck! ---------- status: open -> pending _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40404> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
