title: Extending python - to swig, not to swig or Cython
body: <p>I found the bottleneck in my python code, played around with psycho etc. Then decided to write a c/c++ extension for performance.</p>
  
  <p>With the help of swig you almost don't need to care about arguments etc. Everything works fine.</p>
  
  <p>Now my question: swig creates a quite large py-file which does a lot of 'checkings' and 'PySwigObject' before calling the actual .pyd or .so code.</p>
  
  <p>Does anyone of you have any experience whether there is some more performance to gain if you hand-write this file or let swig do it. </p>