On Fri, 2004-05-07 at 02:10, Fred L. Drake, Jr. wrote: > On Friday 07 May 2004 12:29 am, Guido van Rossum wrote: > > I have a different POV. I don't think there is a compelling reason to > > change this attribute into a set (I doubt it's so time-critical as to > > make a difference) and given that the attribute isn't flagged as > > "private" by having a name starting with underscore, I think the > > change ought to be reverted. > > I'd like to suggest that we either document the "right way" to extend the > information to support new URL schemes, and possibly add a function as the > way to do that. Having to update a whole set of lists from outside the > module seems a poor and error-prone way to do this. It sounds like appending to the list was the right way up until now. That is, extending the list of protocols is a reasonable feature and using a list with a non-underscore name provided one obvious was to do that. Jeremy
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