Message265572
| Author | tylercrompton |
|---|---|
| Recipients | martin.panter, meador.inge, python-dev, twouters, tylercrompton |
| Date | 2016-05-15.03:36:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1463283407.51.0.101432424374.issue26870@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I suppose the only thing that could be left is adding remarks in the documentations for previous versions. If I understand correctly, this would only be added to the documentations for Python 2.7 and 3.5. Is this correct? Since this is the first issue in which I've submitted a patch, I'm still quite new to the CPython development workflow; is there a special way to indicate that a patch should be applied to a branch other than default? Or is that done simply by informally indicating so in a message? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-05-15 03:36:47 | tylercrompton | set | recipients: + tylercrompton, twouters, meador.inge, python-dev, martin.panter |
| 2016-05-15 03:36:47 | tylercrompton | set | messageid: <1463283407.51.0.101432424374.issue26870@psf.upfronthosting.co.za> |
| 2016-05-15 03:36:47 | tylercrompton | link | issue26870 messages |
| 2016-05-15 03:36:47 | tylercrompton | create | |