Databases
StackOverflow2013
Postsdbo
PODo you need to use __init__.py to import a class from a module within a package cleanly?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODo you need to use __init__.py to import a class from a module within a package cleanly?
    primarykey
    data
    text
    <p>Say I have a src folder, and a package named Foo, with a module named Foo containing a class also named Foo. Then in the src folder I have a main module that wants to have the Foo class directly in its namespace.</p> <pre><code>-src -Foo __init__.py Foo.py main.py </code></pre> <p>I believe I could do something like this</p> <p>main.py</p> <pre><code>from Foo.Foo import Foo </code></pre> <p>or add this to the packages init</p> <pre><code>import Foo </code></pre> <p>or</p> <pre><code>from Foo import Foo </code></pre> <p>then in main I could try</p> <pre><code> from Foo import Foo </code></pre> <p>But ideally I would like to be able to just put</p> <pre><code>import Foo </code></pre> <p>in main.py and have that class available directly as Foo (not Foo.Foo)</p> <p>Maybe its not a best practice to name a package, module, and class all the same, but it seems like I have run into situations where it does make sense. I also know I should probably make the module name all lowercase, but I kept it like that for this example.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMark
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThere isn't any way to make `import Foo` import a class and not a module. What you said in your last paragraph is on the right track. Why do you feel you need a package for this? If you just use a module then `from foomodule import Foo` is brief enough.
      singulars
      1. PODo you need to use __init__.py to import a class from a module within a package cleanly?
      1. USBrenBarn
    2. COthat makes sense. i guess it just seems like keeping things in packages is a neat idea.maybe i was thinking about a package where the class itself relies on other modules and maybe even sub packages within it, and being able to just get that class imported. for instance if i have a package for connecting to a db in sql alchemy, and the class uses models imported from modules within the package.
      singulars
      1. PODo you need to use __init__.py to import a class from a module within a package cleanly?
      1. USMark
    3. COThe more stuff you have in your package, the less sense it makes to have `import package` magically import just one of those things instead of importing the actual package. If you need a package to hold multiple modules, great, but then you need to say which modules you want to import, or what stuff you want to import from each. Just try doing it the normal Pythonic way with an appropriate naming scheme. I think you'll find it's not actually that much of a hardship to do `from foomodule import Foo` once at the top of your program.
      singulars
      1. PODo you need to use __init__.py to import a class from a module within a package cleanly?
      1. USBrenBarn
 

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