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 pitrou
Recipients barry, eli.bendersky, eric.smith, ethan.furman, mrabarnett, pitrou, r.david.murray, rhettinger, theller, tim.peters, vstinner
Date 2013-09-09.20:02:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378756971.2502.10.camel@fsol>
In-reply-to <1378756818.02.0.797259779826.issue18986@psf.upfronthosting.co.za>
Content
> +10 to make this a PEP so that more people have a chance to express
> their opinion (currently only those who noticed it on the issues
> mailing list). I find the issue tracker a very bad medium for any kind
> of brain-storming or bikeshedding.

Well, I don't think there is a lot of brainstorming to be done here: we
are talking about a single well-defined functionality. I don't mind
writing a PEP if other people ask for it, but I'd rather spend my time
on more important things.

As for bikeshedding, there is no "good medium" for it, really :-) At
worse we could ask python-dev for their naming contributions (a great
idea, surely).
History
Date User Action Args
2013-09-09 20:02:54pitrousetrecipients: + pitrou, tim.peters, barry, theller, rhettinger, vstinner, eric.smith, mrabarnett, r.david.murray, eli.bendersky, ethan.furman
2013-09-09 20:02:54pitroulinkissue18986 messages
2013-09-09 20:02:53pitroucreate