Ned Deily <> added the comment:

It's been three months since Anthony raised the question about whether this was 
an acceptable ABI change in 3.6.4.  Since then, I am not aware of any reports 
of problems this has caused and there has been no agreement that it is a 
critical problem.  Since 3.6.5rc1 has now been released without this being 
resolved, I'm going to close this issue and hope for the best.  Thanks, 
everyone!  Feel free to reopen if a real life problem can be demonstrated.

priority: deferred blocker -> 
stage: patch review -> resolved
status: open -> closed

Python tracker <>
Python-bugs-list mailing list

Reply via email to