On Jun 10, 2019, at 23:41, Mariatta <maria...@python.org> wrote: > On Mon, Jun 10, 2019 at 8:19 PM Jeffrey Kintscher <websur...@surf2c.net> > wrote: >> A hypothetical example would be two different issues whose descriptions >> appear to be for different behaviors, but are actually caused by the same >> underlying chunk of problematic code being called in different ways. It >> could be something trivial like a corner case not being handled. > Hmm, I personally would still consider the additional issues as duplicates. > So I would make note in each of the duplicate issue saying "this is caused by > the same problem as bpo-X", and close them, and attach the PR only to one bpo > ticket. > To decide which one I would keep open, perhaps the oldest one, but maybe it > depends. Perhaps whichever that seems to contain most detailed info?
I agree. If it seems better to solve everything in one PR, I would generally associate the PR with one issue and close the others as duplicates with explanations why. -- Ned Deily n...@python.org -- [] _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/LGOT7ID2QQC5FPY77YVX3MH3N3WZUEY2/
