See my pull request (ofosos) on Github.
Cheers, Mark On Mon, May 29, 2017 at 7:05 PM, Roberto De Ioris <robe...@unbit.it> wrote: > > > 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 > -- Mark Meyer Systems Engineer mark.me...@smaato.com Smaato Inc. San Francisco – New York – Hamburg – Singapore www.smaato.com Valentinskamp 70, Emporio, 19th Floor 20355 Hamburg T: 0049 (40) 3480 949 0 F: 0049 (40) 492 19 055 The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.
_______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
