This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Al.Sweigart, littleq0903, louielu, markroseman, ned.deily, paulsfo, roger.serwy, serhiy.storchaka, suddha.sourav, taleinat, terry.reedy
Date 2017-06-14.04:14:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Now that I know how to backport with confidence, and have cleared the backlog, and synched 3.6 with 3.7, I want to review this next.  I would like to get it in 6.2, but 6.2 was due yesterday, but delayed, and there is no info on how long the delay is.  This may be one of the harder patches to review and test, but I will try tomorrow. (Its midnight here now.)

My main concern is that we not break one thing while fixing another, which I have done before, due to inadequate tests.  I will try to develop a test protocol from doc subsection 2.2 Completions to list what works without the patch.
Date User Action Args
2017-06-14 04:14:23terry.reedysetrecipients: + terry.reedy, taleinat, ned.deily, roger.serwy, markroseman, Al.Sweigart, serhiy.storchaka, littleq0903, suddha.sourav, paulsfo, louielu
2017-06-14 04:14:23terry.reedysetmessageid: <>
2017-06-14 04:14:23terry.reedylinkissue15786 messages
2017-06-14 04:14:22terry.reedycreate