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 tim.peters
Recipients agthorr, belopolsky, christian.heimes, ethan.furman, georg.brandl, gregory.p.smith, gvanrossum, janzert, mark.dickinson, ncoghlan, oscarbenjamin, pitrou, ronaldoussoren, sjt, skrah, steven.daprano, stutzbach, terry.reedy, tim.peters, tshepang, vajrasky
Date 2013-10-14.01:24:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381713865.19.0.776912919318.issue18606@psf.upfronthosting.co.za>
In-reply-to
Content
Do what's best for the future of the module.  A PEP is more of a starting point than a constraint, especially for implementation details.  And making a private thing public later is one ginormous whale of a lot easier than trying to remove a public thing later.  "Practicality beats purity" once again ;-)
History
Date User Action Args
2013-10-14 01:24:25tim.peterssetrecipients: + tim.peters, gvanrossum, georg.brandl, terry.reedy, gregory.p.smith, ronaldoussoren, mark.dickinson, ncoghlan, belopolsky, pitrou, agthorr, christian.heimes, stutzbach, steven.daprano, sjt, skrah, ethan.furman, tshepang, janzert, oscarbenjamin, vajrasky
2013-10-14 01:24:25tim.peterssetmessageid: <1381713865.19.0.776912919318.issue18606@psf.upfronthosting.co.za>
2013-10-14 01:24:25tim.peterslinkissue18606 messages
2013-10-14 01:24:25tim.peterscreate