➜

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 martin.panter
Recipients josh.r, mark.dickinson, martin.panter, python-dev, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2016-02-03.21:20:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454534411.12.0.793556774244.issue26194@psf.upfronthosting.co.za>
In-reply-to
Content 
I thought the 3.6.0 NEWS file generally listed bugs fixed since (at least) the 3.5.0 release. But the NEWS in default has no mention of Issue 26194.

Serhiy is right that there is nothing more to do for the merging problem. I was just pointing out that something in your “merge” commit must have not worked properly. Normally a merge looks like revision 58266f5101cc (there are two parents listed). But in this case I pulled from default expecting to get all the 3.5 changes as well, but never got your latest 3.5 change until I pulled it explicitly.
History
Date User Action Args
2016-02-03 21:20:11martin.pantersetrecipients: + martin.panter, tim.peters, rhettinger, mark.dickinson, vstinner, python-dev, serhiy.storchaka, josh.r
2016-02-03 21:20:11martin.pantersetmessageid: <1454534411.12.0.793556774244.issue26194@psf.upfronthosting.co.za>
2016-02-03 21:20:11martin.panterlinkissue26194 messages
2016-02-03 21:20:10martin.pantercreate