title: ImportError - Using Python Packages at the same level
body: <p>I have two Python packages where one needs to be imported by the other.  The directory structure is like follows:</p>
  
  <pre><code>workspace/
    management/
      __init__.py
      handle_management.py
      other_management.py
    utils/
      __init__.py
      utils_dict.py
  </code></pre>
  
  <p>I'm trying to import functionality from the <code>utils</code> project in the <code>handle_management.py</code> file:</p>
  
  <pre><code>import utils.utils_dict
  </code></pre>
  
  <p>Error I'm getting when trying to run <code>handle_management.py</code>:</p>
  
  <pre><code>ImportError: No module named utils.utils_dict
  </code></pre>
  
  <p>I've read a lot about how to resolve this problem and I can't seem to find a solution that works.</p>
  
  <p>I started with <a href="https://stackoverflow.com/questions/279237/python-import-a-module-from-a-folder">Import a module from a relative path</a> - I tried the applicable solutions but none worked.</p>
  
  <p>Is the only solution to make <code>workspace/</code> available via <code>site_packages</code>?  If so, what is the best way to do this?</p>
  
  <p>EDIT:</p>
  
  <p>I've tried to add the <code>/home/rico/workspace/</code> to the <code>PYTHONPATH</code> - no luck.</p>
  
  <p>EDIT 2:</p>
  
  <p>I was able to successfully use klobucar's solution but I don't think it will work as a general solution since this utility is going to be used by several other developers.  I know I can use some Python generalizations to determine the relative path for each user.  I just feel like there is a more elegant solution.</p>
  
  <p>Ultimately this script will run via cron to execute unit testing on several Python projects.  This is also going to be available to each developer to ensure integration testing during their development.</p>
  
  <p>I need to be able to make this more general.</p>
  
  <p>EDIT 3:</p>
  
  <p>I'm sorry, but I don't really like any of these solutions for what I'm trying to accomplish.  I appreciate the input - and I'm using them as a temporary fix.  As a complete fix I'm going to look into adding a script available in the <code>site_packages</code> directory that will add to the <code>PYTHONPATH</code>.  This is something that is needed across several machines and several developers.</p>
  
  <p>Once I build my complete solution I'll post back here with what I did and mark it as a solution.</p>
  
  <p>EDIT 4:</p>
  
  <p>I feel as though I didn't do a good job expressing my needs with this question.  The answers below addressed this question well - but not my actual needs.  As a result I have restructured my question in another post.  I considered editing this one, but then the answers below (which would be very helpful for others) wouldn't be meaningful to the change and would seem out of place and irrelevant.</p>
  
  <p>For the revised version of this question please see <a href="https://stackoverflow.com/questions/10637458/unable-to-import-python-package-universally#comment13789797_10637458">Unable to import Python package universally</a></p>