> Just to note, this is uwsgi 2.0.15. The error seems like a kind of "hard" > error. When I connect to the running socket, every tracebacker thread will > write > > *** uWSGI Python tracebacker output *** > > and then never respond again. > > Cheers, Mark > >
Hi Mark, unfortunately the tracebacker has never been ported to python 3. Feel free to open an issue on github, it should not be an heavy task now that the vast majority of the uwsgi components are battle tested on py3 -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
