Ezio Melotti <ezio.melo...@gmail.com> added the comment: Even if knowing the module(s) related to the issue is useful, there are a number of problems that should be considered: * there are hundreds of modules; * there's no easy way to display so many options; * several modules can be related to the issue; * there are different modules depending on the Python version; * there are different names for the same modules depending on the Python version; * the list of modules must be updated when modules are added/removed/renamed; * a new field adds clutter to the UI and more work for the submitters and triagers; * searching for a specific module won't include the issues if the field is not set correctly (i.e. old issues and issues that haven't be triaged), the normal search will; * there's no patch ready to implement (or attempt to implement) this feature;
Another option is looking automatically at the attached patches, figure out what files they affect, and make this information available. This won't require extra work for submitters and triagers and no new fields are needed in the issue page (only a field in the search page). ---------- nosy: +ezio.melotti status: unread -> chatting _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue373> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org http://mail.python.org/mailman/listinfo/tracker-discuss
