[issue40242] zmq mysql core dump

Eric V. Smith added the comment: I'm going to close this. If you can provide information on how to reproduce this and/or what you observe in the segfault dump, we will happily reopen it. I think the best "resolution" tag is to call this "third party", but I'm not sure it matters too much. -

[issue40242] zmq mysql core dump

Rohit Gupta added the comment: For the time being, changing the order of import is solving the problem. -- ___ Python tracker ___ _

[issue40242] zmq mysql core dump

Eric V. Smith added the comment: This looks like a problem in zmq, pyzmq, or mysql-connector-python, not in python itself. I'd suggest asking in a mysql-connector-python specific location for starters. You should also try to duplicate the problem without importing zmq, which doesn't seem to

[issue40242] zmq mysql core dump

New submission from Rohit Gupta : # pyzmq==19.0.0 # zmq==0.0.0 # mysql-connector-python==8.0.19 # Following code is resulting in # Segmentation fault (core dumped) ## import zmq import mysql.connector database = "dev" host = "192.168.56.1" port = 3306 user = "u