Edward Loper wrote: > I thought that it would be more efficient to get feedback on whether the > patch is a good idea before writing the docs & tests. But I guess that > that's now how things are done w/ Python development. I'll go ahead and > add test cases & docs, and update the patches. It's more efficient for the patch submitter, but less efficient for the reviewer, because the reviewer needs to spend more time understanding the patch in detail. Therefore, patches that are formally complete get better attention; patches where the author couldn't find the time to write documentation might never get reviewed. Regards, Martin
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