As @ZeroIntensity asked in #158748 (comment), this is the single issue for the reports I filed in bulk on 4 October (UTC), #158695 to #158785. I'm sorry for the flood: my tool filed them one after another and I should not have let it. It now files nothing here while this issue is open, and never more than one report per project at a time.
The findings are compiled in one place, with a table of every result, its verdict and a link to its reproducer and output: https://github.com/augusto-rehfeldt/bugforge-results (I used that repository rather than a gist; it is the same list.)
What they are: an automated property-testing tool I run (bugforge) reads a module's documentation, searches for an input that breaks a documented property, and writes a standalone reproducer. Every reproducer in the list was executed on Python 3.14.6 on Windows, and its output is in the linked folder and in the closed issue.
What they are not: reviewed. The reports were written by a language model and nobody, including me, has checked each one by hand. I expect a good share to be duplicates, intended behaviour, or inputs too contrived to matter, and several findings in the same module are probably one defect.
I won't open separate issues or pull requests for any of these unless a maintainer of the module asks for one here. If the list is not wanted at all, please close this and nothing more will follow.
(This text was drafted with an AI assistant.)
As @ZeroIntensity asked in #158748 (comment), this is the single issue for the reports I filed in bulk on 4 October (UTC), #158695 to #158785. I'm sorry for the flood: my tool filed them one after another and I should not have let it. It now files nothing here while this issue is open, and never more than one report per project at a time.
The findings are compiled in one place, with a table of every result, its verdict and a link to its reproducer and output: https://github.com/augusto-rehfeldt/bugforge-results (I used that repository rather than a gist; it is the same list.)
What they are: an automated property-testing tool I run (bugforge) reads a module's documentation, searches for an input that breaks a documented property, and writes a standalone reproducer. Every reproducer in the list was executed on Python 3.14.6 on Windows, and its output is in the linked folder and in the closed issue.
What they are not: reviewed. The reports were written by a language model and nobody, including me, has checked each one by hand. I expect a good share to be duplicates, intended behaviour, or inputs too contrived to matter, and several findings in the same module are probably one defect.
I won't open separate issues or pull requests for any of these unless a maintainer of the module asks for one here. If the list is not wanted at all, please close this and nothing more will follow.
(This text was drafted with an AI assistant.)