2010/11/17 Michael Foord <fuzzyman at voidspace.org.uk>: > So -1 on splitting Python development style guide into multiple documents. I don't think that the publicness or API stability promises of the standard library are part of a style guide. They're an essential part of the library documentation. They aren't a guide for 3rd-party code, and are specific to the standard library. If we can't come up with something reasonable for the standard library, we *certainly* shouldn't be making recommendations on the matter for 3rd party code. If we do come up with something reasonable, we can recommend it to others later (once field-proven), and without duplication. (Possibly by referring to the standard library documentation, and possibly by refactoring. That's not important until we have something, though.) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> "A storm broke loose in my mind." --Albert Einstein
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