Brett Cannon wrote: > Well, I don't know if that is necessarily the case. PEP 360 doesn't > have a single project saying that minor fixes can just go right in. If > we want to just change the wording such that all code in the tree can be > touched for bug fixes and compatibility issues without clearance, that's > great. I think this is what Philipp Eby essentially said about wsgiref (re-read the subject line for reference). If the external maintainer really has a strict "don't change anything" policy, the only reasonable way to enforce this policy is to withdraw the code. > But Phillip's email that sparked all of this was about basic changes to > wsgiref, not some API change (at least to the best of my knowledge). That's my understanding as well. 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