[MvL] > I think *anybody* should submit patches to SF first unless you are > 100% sure that the patch fixes the problem in an undebatable way, and > perhaps unless it is you. > > Being able to say "this is fine, please check it in (replacing the C++ > style comment with a C style comment)" already helps reducing the load > on the reviewer. > > Unless the new contributors are very careful, I'm sure they will break > the CVS sooner or later. Unless this happens a week before the 2.3 > release, I have no problem with that. I think I see consensus to give the new folks checkin permission right away, but encourage them to submit their code to the SF patch manager first until they've got the hang of it. Skip, can you tell them this? --Guido van Rossum (home page: http://www.python.org/~guido/)
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