| リビジョン | 58fbcdb582d0365c70a8e04c73a62cb1bed013fd (tree) |
|---|---|
| 日時 | 2024-02-19 02:14:40 |
| 作者 | Albert Mietus < albert AT mietus DOT nl > |
| コミッター | Albert Mietus < albert AT mietus DOT nl > |
The summary of the (py,compiler) package structure is more-or-less done (DOC-only)
| @@ -78,12 +78,12 @@ | ||
| 78 | 78 | Packages that are optional, or where alternatives are available, are conveniently bundled in an extra ‘layer’: |
| 79 | 79 | |
| 80 | 80 | - ``from castle.readers import typicalReader as reader`` |
| 81 | -- ``from castle.readers import mockReader as reader`` | |
| 82 | - |BR| | |
| 83 | - Although some would vote for ``from castle.readers.mocks import reader`` for the latter. | |
| 81 | +- ``from castle.TESTDOUBLES.readers import mockReader as reader`` (selected option for mocks) | |
| 82 | +- ``from castle.readers import mockReader as reader`` (alternative, not preferred) | |
| 84 | 83 | |
| 85 | -The “dotted names” gives the user/sw-engineer an hint on which (sub)packages are available, and where it fits. Aside of | |
| 86 | -that, the name is not very important -- the functionality doesn't depend on it. | |
| 84 | + | |
| 85 | +The “dotted names” gives the user/SW-engineer an hint on which (sub)packages are available, and where it fits. Aside of | |
| 86 | +that, the name is not very important. During importing we can even *rename* a package, with the `as <name>` langage feature. | |
| 87 | 87 | |
| 88 | 88 | .. note:: The functionality does not depend on the name! |
| 89 | 89 |
Fork
CCastle/DocParts/Design/01.Architecture/02.packages.rst