Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>"I drew a diagram of the import dependencies, and I was planning to aggregate classes by layer level."</strong></p> <p>Python must read like English (or any other natural language.)</p> <p>An import is a first-class statement that should have real meaning. Organizing things by "layer level" (whatever that is) should be clear, meaningful and obvious.</p> <p>Do not make arbitrary technical groupings of classes into modules and modules into packages. </p> <p>Make the modules and package obvious and logical so that the list of imports is obvious, simple and logical.</p> <p><strong>"Also, I was considering some modification to the classes so to reduce these dependencies."</strong></p> <p>Reducing the dependencies sounds technical and arbitrary. It may not be, but it sounds that way. Without actual examples, it's impossible to say.</p> <p>Your goal is clarity. </p> <p>Also, the module and package are the stand-alone units of reuse. (Not classes; a class, but itself isn't usually reusable.) Your dependency tree should reflect this. You're aiming for modules that can be imported neatly and cleanly into your application.</p> <p>If you have many closely-related modules (or alternative implementations) then packages can be used, but used sparingly. The Python libraries are relatively flat; and there's some wisdom in that.</p> <hr> <p><strong>Edit</strong></p> <p>One-way dependency between layers is an essential feature. This is more about proper software design than it is about Python. You should (1) design in layers, (2) design so that the dependencies are very strict between the layers, and then (3) implement that in Python. </p> <p>The packages may not necessarily fit your layering precisely. The packages may physically be a flat list of directories with the dependencies expressed only via <code>import</code> statements.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to properly organize a package/module dependency tree?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USS.Lott
    1. USS.Lott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to properly organize a package/module dependency tree?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COWith layers I mean organize my packages so that their classes/modules depend either on that package's stuff, or another one which contains "lower" services. I would consider every package as an "independent library", eventually depending on other Packages, so not to have circular dependencies.
      singulars
      1. PO
      1. USStefano Borini
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload