title: Typical Naming Conventions for Python Directories in Packages
body: <p><strong>The Question</strong><br>
  I would like to know if there is a standard convention for the naming of Python directories that plan to be imported as a module.  Meaning the directory contains a blank <code>__init__.py</code></p>
  
  <p><strong>Background</strong><br>
  Up until recently I have given it little thought and named solely based on what made sense at the file system level.  What got me in trouble is that what made sense at the file system level also made sense for other developers' standalone modules.  Consider the following directory:  </p>
  
  <pre><code>+ drivers
      + prologix  
          - __init__.py
          - driver_a.py
          - driver_b.py
      + visa
          - __init__.py  
          - driver_a.py
          - driver_b.py
      __init__.py
      ringout.py &lt;-- simple file to ring-out the drivers  
  </code></pre>
  
  <p>While this worked fine when ringing out the prologix's drivers, I ran into an issue when trying to import my visa drivers as well as pyVisa's 'visa' module.  It was very easy to diagnose the problem, but the fix to rename my visa driver's folder to 'visa_dir' makes the code more difficult to read (IMO).  </p>
  
  <pre><code>import drivers.visa  
  </code></pre>
  
  <p>vs  </p>
  
  <pre><code>import drivers.visa_dir  
  </code></pre>
  
  <p><strong>Is there a better way to handle this?</strong></p>