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 Friedrich.Spee.von.Langenfeld, SilentGhost, Yoni Lavi, belopolsky, berker.peksag, docs@python, ezio.melotti, nharold, r.david.murray, rhettinger, terry.reedy
Date 2016-06-03.19:42:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464982965.38.0.828264274155.issue22558@psf.upfronthosting.co.za>
In-reply-to
Content
For me, the issue is willingness, not permission ;-).  Reviewing a patch includes somehow indicating changes needed to apply it 'today', and a revised patch is the best way.  Please say whether the header changes are in 3.6 only (in which case a separate 3.5 patch is needed) or in both.  'Commit ready' means that you believe a core dev could (and should) download, apply without issue, and commit when satisfies.  I should do so within a week if no one else does.
History
Date User Action Args
2016-06-03 19:42:45terry.reedysetrecipients: + terry.reedy, rhettinger, belopolsky, ezio.melotti, r.david.murray, SilentGhost, docs@python, berker.peksag, Friedrich.Spee.von.Langenfeld, Yoni Lavi, nharold
2016-06-03 19:42:45terry.reedysetmessageid: <1464982965.38.0.828264274155.issue22558@psf.upfronthosting.co.za>
2016-06-03 19:42:45terry.reedylinkissue22558 messages
2016-06-03 19:42:45terry.reedycreate