Ned Deily <> added the comment:

Thanks for the report and the good detective work!  I see the same results.  It 
appears that the error was introduced by 
c5ae169e1b73315672770517bf51cf8464286c76 for Issue26439.  It looks we need both 
a fix and a test for this.  This really needs to be fixed for 3.7.0b4.

nosy: +Michael.Felt, ned.deily, vstinner
priority: normal -> release blocker
stage:  -> needs patch

Python tracker <>
Python-bugs-list mailing list

Reply via email to