A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-September/104044.html below:

[Python-Dev] Goodbye

[Python-Dev] GoodbyeAntoine Pitrou solipsis at pitrou.net
Fri Sep 24 16:50:58 CEST 2010
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"?

cheers

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4