➜

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 amaajemyfren
Recipients Chas Belov, amaajemyfren, docs@python
Date 2020-05-24.11:41:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKyeSh3xT3MzM9YnQWn8ZrurCWTjdVoAdxT0=CFE53WjUCVf8A@mail.gmail.com>
In-reply-to <1590278061.1.0.686702454601.issue40748@roundup.psfhosted.org>
Content 
On Sun, May 24, 2020 at 2:54 AM Chas Belov <report@bugs.python.org> wrote:

> Do I need a separate issue for each code block that is not common across
3.5 through 3.10? Or would this be handled during the back-porting process?

Unless there is an issue, automatic back-porting should handle it.
PR against master(dev/3.10) should be enough.
History
Date User Action Args
2020-05-24 11:41:51amaajemyfrensetrecipients: + amaajemyfren, Chas Belov
2020-05-24 11:41:51amaajemyfrenlinkissue40748 messages
2020-05-24 11:41:50amaajemyfrencreate