On Thu, 2021-08-19 at 11:41 +0100, Irit Katriel wrote:
> Well, in order to verify that we fixed the problem you reported we
> need to be able to test the fix and see that the problem is gone. 
> Right now we have two theories of what the cause could be, because
> there are two known bugs in that area. But you may have stumbled upon
> an unrelated third bug.
> 
> The best scenario is that we close a bpo issue because we can
> reproduce the bug and see that it has been fixed. When that's not
> possible, there will come a point where we will close it and say "the
> code has changed since you observed the problem and we fixed things
> that could have caused it. Please open a new issue if you still see
> this bug".

That's fair. I'll do my best to reproduce it and see which (if either)
change resolves it.

Duncan.

-- 
Duncan Grisby <dun...@grisby.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/YKKJ4RD376UEC7LYN6BAMHVTK55XHYXU/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to