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 RubyTuesdayDONO
Recipients RubyTuesdayDONO, dmalcolm, gregory.p.smith
Date 2013-12-13.13:19:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Sat, Dec 7, 2013 at 1:35 PM, Gregory P. Smith <>
> I fixed this in 3.3 and 3.4 several weeks ago.

Sorry for the duplicate message a few moments ago … "fat-fingered" my send

So, has the fix just not reached the Portage tree yet? I don't fully
understand how upstream commits reach Portage, and would appreciate any
direction you might have to avoid reporting something already fixed.
Date User Action Args
2013-12-13 13:19:18RubyTuesdayDONOsetrecipients: + RubyTuesdayDONO, gregory.p.smith, dmalcolm
2013-12-13 13:19:18RubyTuesdayDONOlinkissue19901 messages
2013-12-13 13:19:17RubyTuesdayDONOcreate