Databases
StackOverflow2013
Postsdbo
POImporting modules: __main__ vs import as module
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POImporting modules: __main__ vs import as module
    primarykey
    data
    text
    <p>To preface, I think I may have figured out how to get this code working (based on <a href="https://stackoverflow.com/questions/12242417/changing-module-variables-after-import">Changing module variables after import</a>), but my question is really about why the following behavior occurs so I can understand what to not do in the future.</p> <p>I have three files. The first is mod1.py:</p> <pre><code># mod1.py import mod2 var1A = None def func1A(): global var1 var1 = 'A' mod2.func2() def func1B(): global var1 print var1 if __name__ == '__main__': func1A() </code></pre> <p>Next I have mod2.py:</p> <pre><code># mod2.py import mod1 def func2(): mod1.func1B() </code></pre> <p>Finally I have driver.py:</p> <pre><code># driver.py import mod1 if __name__ == '__main__': mod1.func1A() </code></pre> <p>If I execute the command <code>python mod1.py</code> then the output is <code>None</code>. Based on the link I referenced above, it seems that there is some distinction between <code>mod1.py</code> being imported as <code>__main__</code> and <code>mod1.py</code> being imported from <code>mod2.py</code>. Therefore, I created <code>driver.py</code>. If I execute the command <code>python driver.py</code> then I get the expected output: <code>A</code>. I sort of see the difference, but I don't really see the mechanism or the reason for it. How and why does this happen? It seems counterintuitive that the same module would exist twice. If I execute <code>python mod1.py</code>, would it be possible to access the variables in the <code>__main__</code> version of <code>mod1.py</code> instead of the variables in the version imported by <code>mod2.py</code>?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMartijn Pieters
    1. USBrendan
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POImporting modules: __main__ vs import as module
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POImporting modules: __main__ vs import as module
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POImporting modules: __main__ vs import as module
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou'll be doing yourself a favor if you refactor to eliminate the circular import.
      singulars
      1. POImporting modules: __main__ vs import as module
      1. USeryksun
 

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