On Sat, Sep 25, 2010 at 12:50 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > Le samedi 25 septembre 2010 à 00:42 +1000, Nick Coghlan a écrit : >> > >> > I have often used searches on "performance" or "resource usage" to find >> > what was needing a review or a patch. I think it would be a mistake to >> > remove those two categories. >> >> That purpose would be served just as well by keywords though >> (particularly since those attributes aren't mutually exclusive - >> resource usage problems will usually *cause* performance problems, and >> you may notice the latter first). >> >> A generic "bug" classification would also better suit documentation >> bugs. The simpler we can make the more common fields, while still >> providing the essential information, the better. > > But how should a performance improvement be filed? Bug? Feature request? > Or should "feature request" be renamed "improvement"?
It's a feature request (since we won't backport it unless there is a genuine performance problem being addressed as a bug fix). Whether that warrants changing the name, I don't know. A third option for "other improvement" may also work (since that would also cover things like clarifying doc wording, fixing comments, adjusting code to be more readable/obviously correct, etc). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com