Raymond Hettinger <raymond.hettinger at gmail.com> writes: > >> Are we permanently locked into the exact ten filenames that are > >> currently used: utils, suite, loader, case, result, main, signals, > >> etc? […] > Sounds like a decision to split a module into a package is a big > commitment. Each of the individual file names becomes a permanent part > of the API. Even future additional splits are precluded because it > might break someones dotted import (i.e. not a single function can be > moved between those files -- once in unittest.utils, alway in > unittest.utils). Is this a case where it would be better if the package names had the leading underscore: ‘_utils’, ‘_suite’, etc.? Does the convention on single-leading-underscore identifiers as “don't rely on this name staying the same in future versions” hold for package names? -- \ “Alternative explanations are always welcome in science, if | `\ they are better and explain more. Alternative explanations that | _o__) explain nothing are not welcome.” —Victor J. Stenger, 2001-11-05 | Ben Finney
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