On Tue, Mar 10, 2009 at 11:43, Terry Reedy <tjreedy at udel.edu> wrote: > Brett Cannon wrote: > >> >> This is somewhat covered by components, but it's implicit. Would it be >> worth making this explicit? I have always wondered if people would be more >> willing to help out if they could easily search for pure Python code issues >> if that is as far as they feel comfortable. >> > > If and when I am ready to move from working on documentation issues (which > seem to becoming fewer as the 3.x transition is completed) to code issues, > that would be helpful. What would be really helpful is to have library > issues tagged and sorted by specific modules (or modules, if more than one), > but I do not know how that might be done. It would have to be a text field that people just filled in. Making a list that had to be kept up-to-date would be a disaster. But one would hope that simply searching for an issue with a specific module name would be enough to warrant not having to have the field. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090310/b1a5db3c/attachment-0001.htm>
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