On 5 December 2016 at 18:42, Armin Rigo <armin.r...@gmail.com> wrote: > In 3.5.2+ at least, I'm reasonably convinced that all crashers are > real, but I didn't spend the time to come up with actual examples or > patches, beyond the first two items on the list. There are also > non-crasher bugs where the current behavior is clearly wrong according > to the documentation or the PEP. I've also added a few points that > strike me as rather strange but not against the documentation. What > should I do with this list? From my point of view, I could drop it > all in a single issue, or possibly three of them (crashers, bugs, > "strange"). Alternatively I can go ahead and open one issue per > bullet point. Which way would you prefer? Or, if you think there is > no point in me filing issues without actual examples and patches, then > that's fine with me too and I will simply continue to expand my > cpython-crashers.rst file.
I think 3 omnibus issues would be a reasonable way to go, with the discussion on those issues then splitting things out to either new issue reports, or entries in https://hg.python.org/cpython/file/default/Lib/test/crashers/ (if any of the crashers can't be readily resolved). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
