Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Although the names used there are different from what's shown in your question's directory structure, you could use my answer to the question titled <a href="https://stackoverflow.com/questions/5117194/python-namespacing-and-classes/5118437#5118437"><em>Namespacing and classes</em></a>. The <code>__init__.py</code> shown there would have also allowed the <code>usepackage.py</code> script to have been written this way (<code>package</code> maps to <code>subdir</code> in your question, and <code>Class1</code> to <code>myclass01</code>, etc):</p> <pre><code>from package import * print Class1 print Class2 print Class3 </code></pre> <p><strong>Revision (updated):</strong></p> <p>Oops, sorry, the code in my other answer doesn't quite do what you want — it only automatically imports the names of any package submodules. To make it also import the named attributes from each submodule requires a few more lines of code. Here's a modified version of the package's <code>__init__.py</code> file (which also works in Python 3.4.1):</p> <pre><code>def _import_package_files(): """ Dynamically import all the public attributes of the python modules in this file's directory (the package directory) and return a list of their names. """ import os exports = [] globals_, locals_ = globals(), locals() package_path = os.path.dirname(__file__) package_name = os.path.basename(package_path) for filename in os.listdir(package_path): modulename, ext = os.path.splitext(filename) if modulename[0] != '_' and ext in ('.py', '.pyw'): subpackage = '{}.{}'.format(package_name, modulename) # pkg relative module = __import__(subpackage, globals_, locals_, [modulename]) modict = module.__dict__ names = (modict['__all__'] if '__all__' in modict else [name for name in modict if name[0] != '_']) # all public exports.extend(names) globals_.update((name, modict[name]) for name in names) return exports if __name__ != '__main__': __all__ = ['__all__'] + _import_package_files() # '__all__' in __all__ </code></pre> <p>Alternatively you can put the above into a separate .py module file of its own in the package directory, and use it from the package's <code>__init__.py</code> like this:</p> <pre><code>if __name__ != '__main__': from ._import_package_files import * # defines __all__ __all__.remove('__all__') # prevent export (optional) </code></pre> <p>Whatever you name the file, it should be something that starts with an <code>_</code> underscore character so it doesn't try to <code>import</code> itself recursively.</p>
    singulars
    1. This table or related slice is empty.
    1. POImporting classes from different files in a subdirectory
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USmartineau
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POImporting classes from different files in a subdirectory
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow that's a rather complex solution for this problem.
      singulars
      1. PO
      1. USliewl
    2. CODoesn't seem to be working for me.
      singulars
      1. PO
      1. USliewl
    3. CO`__init__.py` is pretty generic, which tends to complicate things (and is why many just hard-code things into their programs). Fortunately it only executes once and its compiled byte-code is saved. I tested it before posting my answer and again before this comment. What seems to be the problem?
      singulars
      1. PO
      1. USmartineau
 

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