> > 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 <songofacandy at gmail.com>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4