Message292792
The warning, which became a failure in 3.6, was averted for 3.6 by #27372. I intentionally did not patch 3.5 and merge forward because the warning was neither unique nor a failure, while adding the merge would have been a considerable bother. Also, I anticipated that the 3.5.3 release after 3.6.0 would be the last 3.5 bugfix release as per normal policy, so that this would be a moot point by now. (And I have no idea why normal policy was not followed.) I think this issue should be closed as any of "duplicate", "out of date", or "won't fix". |
|
Date |
User |
Action |
Args |
2017-05-02 17:48:52 | terry.reedy | set | recipients:
+ terry.reedy, paul.moore, vstinner, tim.golden, zach.ware, steve.dower |
2017-05-02 17:48:52 | terry.reedy | set | messageid: <1493747332.9.0.708432482278.issue30233@psf.upfronthosting.co.za> |
2017-05-02 17:48:52 | terry.reedy | link | issue30233 messages |
2017-05-02 17:48:52 | terry.reedy | create | |
|