title: How to minimize the Python 3.6 runtime for an embedded system?
body: <p>We make an ARM 9 embedded system, Linux, etc. Recently a customer asked we pre-install Python 3 for them. We worked out the cross-compile (QEMU is really magical), but the resultant build is 177Mb, so that's a no go. What's the best plan here - we can leave off the Doc directory, and maybe the "build" dir? I see the Lib directory is 54Mb - is it a case of picking an choosing what libs the customer needs? We know very little about Python. To be clear, I see lots of advice about packaging Python apps - that's not what we are doing - we are packaging the Python runtime. Thanks! (directory size summary below)</p>
  
  <blockquote>
  <pre><code>1.6M  ./Python-3.6.0/Mac
  760K  ./Python-3.6.0/Include
  17M   ./Python-3.6.0/build
  5.4M  ./Python-3.6.0/Python
  8.0K  ./Python-3.6.0/.github
  54M   ./Python-3.6.0/Lib
  2.7M  ./Python-3.6.0/PC
  2.7M  ./Python-3.6.0/Tools
  6.9M  ./Python-3.6.0/Objects
  11M   ./Python-3.6.0/Doc
  824K  ./Python-3.6.0/Parser
  20M   ./Python-3.6.0/Modules
  15M   ./Python-3.6.0/Programs
  620K  ./Python-3.6.0/PCbuild
  12K   ./Python-3.6.0/Grammar
  5.8M  ./Python-3.6.0/Misc
  161M  ./Python-3.6.0
  177M  .
  </code></pre>
  </blockquote>