title: Pymqi throws exception ImportError at library import
body: <p>I'm getting strange ImportError exception while importing to my script pymqi.</p>
  
  <ol>
  <li>I installed WebSphere MQ for windows 7.5, both user and client versions.</li>
  <li>I tried to run pip install pymqi, but there was problems at C++ compiling. </li>
  <li>I moved headers from <code>C:\Program Files (x86)\IBM\WebSphere MQ\tools\c\include</code> to <code>C:\Python27\include</code> and tried to run, there were linking problem.</li>
  <li>I moved some <code>.lib</code> files from <code>C:\Program Files (x86)\IBM\WebSphere MQ\tools\Lib</code> to <code>C:\Python27\libs</code> and it compiled well.</li>
  </ol>
  
  <p>Then I tried this code:</p>
  
  <pre><code>import pymqi
  queue_manager = "QM"
  channel = "SVRCONN"
  host = "192.168.1.252"
  port = "1434"
  conn_info = "%s(%s)" % (host, port)
  qmgr = pymqi.connect(queue_manager, channel, conn_info)
  qmgr.disconnect()
  </code></pre>
  
  <p>And at import library I got:</p>
  
  <pre><code>  File "build\bdist.win32\egg\pymqe.py", line 7, in &lt;module&gt;
    File "build\bdist.win32\egg\pymqe.py", line 6, in __bootstrap__
  ImportError: DLL load failed: �� ������ ��������� ������.
  </code></pre>
  
  <p>Where after some manipulations I got that <code>...��...</code> means: it can't find module.</p>
  
  <ol start="5">
  <li>I decide that done something wrong. Downloaded <a href="https://pypi.python.org/pypi/pymqi" rel="nofollow">pymqi-1.3</a> and done <code>setup.py build</code> + <code>setup.py install</code>, that finished successfully. But problem still was there.</li>
  <li>I moved all DLL files from <code>C:\Program Files (x86)\IBM\WebSphere MQ\bin</code> to <code>C:\Python27</code></li>
  </ol>
  
  <p>And got another ImportError exception with text, that may be translated as "Bad try to access to memory address".</p>
  
  <ol start="7">
  <li>I tried springpython library, but it uses pymqi inside, so falls with same exceptions.</li>
  </ol>
  
  <p>How can I finally solve this problem? I guess there may be problem at WebSphere side, but how to check it? "WS Explorer" runs well.</p>