title: The problem with installing PIL using virtualenv or buildout
body: <p>When I install PIL using easy_install or buildout it installs in such way, that I must do 'import Image', not 'from PIL import Image'.</p>
  
  <p>However, if I do "apt-get install python-imaging" or use "pip -E test_pil install PIL", all work fine.</p>
  
  <p>Here are examples of how I trying to install PIL using virtualenv:</p>
  
  <pre><code># virtualenv --no-site-packages test_pil
  # test_pil/bin/easy_install PIL
  # test_pil/bin/python
  Python 2.5.1 (r251:54863, Feb  6 2009, 19:02:12) 
  [GCC 4.0.1 (Apple Inc. build 5465)] on darwin
  Type "help", "copyright", "credits" or "license" for more information.
  &gt;&gt;&gt; import PIL
  Traceback (most recent call last):
    File "&lt;stdin&gt;", line 1, in &lt;module&gt;
  ImportError: No module named PIL
  </code></pre>
  
  <p>I see, that easy_install pack PIL into the Egg, and PIP does not. Same thing with buildbot, it uses eggs.</p>
  
  <p>How could I install PIL properly, using easy_install or buildout?</p>