> > It's also possible that the fault is not in sending (we have evidence here > that two entirely different protocols have not received it, and they are also > not in the archives [1]), but in the generation of the report. Could there > have been a subtle change to the bpo tracker itself, or something else along > those lines, that is causing the script to fail silently before it ever > reaches the point of attempting to send? Or perhaps a disk ran out of space > somewhere? > > [1] https://mail.python.org/pipermail/python-dev/2019-February/date.html
I suspect so. See "Open issues deltas (weekly)" graph in this page. It is ended by 2/8. https://bugs.python.org/issue?@template=stats -- INADA Naoki <songofaca...@gmail.com> _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
