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 docs@python, eric.frederich, eric.smith, miss-islington, python-dev, terry.reedy
Date 2020-08-05.21:41:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596663664.66.0.765727980276.issue41482@roundup.psfhosted.org>
In-reply-to
Content
The issue resulting in the addition of a "backport-52f9842-3.9" branch to the main python/cpython repository.  I believe that this is a mistake and should be removed, but I don't know how.

When miss-islington fails to backport for reasons other than a merge conflict, the problem is likely transient  -- perhaps a timing issue or temporary resource unavailable issue that we have no control over.  The solution is to delete the backport label, close the label box, reopen the label box, add the label, and reclose.  I did this and the auto backport was generated.  (The 3.8 backport is ready to approve and merge.)
History
Date User Action Args
2020-08-05 21:41:04terry.reedysetrecipients: + terry.reedy, eric.smith, docs@python, python-dev, eric.frederich, miss-islington
2020-08-05 21:41:04terry.reedysetmessageid: <1596663664.66.0.765727980276.issue41482@roundup.psfhosted.org>
2020-08-05 21:41:04terry.reedylinkissue41482 messages
2020-08-05 21:41:04terry.reedycreate