[issue10767] Lib/test/crashers/README is out of date
Georg Brandl ge...@python.org added the comment: Fixed in r87530. -- nosy: +georg.brandl resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10767] Lib/test/crashers/README is out of date
Brett Cannon br...@python.org added the comment: That's a fair assessment. A lot of the bugs that are easy to fix got closed out a couple of years back. The rest are (I think) considered too difficult and too marginal to worry about. -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10767] Lib/test/crashers/README is out of date
New submission from Alexander Belopolsky belopol...@users.sourceforge.net: Among other things, README says: Each test should have a link to the bug report: # http://python.org/sf/BUG# but the only such link is found in crashers/infinite_loop_re.py and points to a closed issue 1541697. It looks like the purpose of Lib/test/crashers has changed from being a repository of outstanding bugs to a repository of crashers that are not considered to be bugs. -- assignee: d...@python components: Documentation, Tests messages: 124586 nosy: belopolsky, d...@python priority: normal severity: normal status: open title: Lib/test/crashers/README is out of date ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com