title: Update to pyodbc 4 causes "Segmentation fault"
body: <p>I have a Django+celery site running on Elastic Beanstalk that used pyodbc 3.  Because of another issue, I had to update to pyodbc 4.</p>
  
  <p>However, the web site starting giving error 500 and this is the information logged:</p>
  
  <pre><code>[Fri Feb 24 20:02:14.448536 2017] [core:notice] [pid 27978] AH00052: child pid 28292 exit signal Segmentation fault (11)
  [Fri Feb 24 20:02:15.145503 2017] [core:error] [pid 27988] [client 205.165.34.225:50040] End of script output before headers: wsgi.py, referer: ...
  </code></pre>
  
  <p>During that time the Celery worker was still running and working just fine!  I've re-deployed the whole server (Rebuild Environment in AWS) and it didn't fix the issue.</p>
  
  <p>I had to revert to pyodbc 3 and it started working just fine.  Any ideas?</p>
  
  <p>django 1.10.4, pyodbc 4.0.11, django-pyodbc-azure 1.10.0.1</p>