# Python Libraries with compiles binaries folder location

**URL:** <https://forum.serverless.com/t/python-libraries-with-compiles-binaries-folder-location/6328>\
**Category:** Serverless Framework\
**Created:** [November 1, 2018, 11:04am UTC](https://forum.serverless.com/t/python-libraries-with-compiles-binaries-folder-location/6328 "2018-11-01T11:04:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![majorgilles](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/majorgilles/32/2717_2.png) [@majorgilles](https://forum.serverless.com/u/majorgilles)\
**Post date:** [November 1, 2018, 11:04am UTC](https://forum.serverless.com/t/python-libraries-with-compiles-binaries-folder-location/6328/1 "2018-11-01T11:04:02Z")

</div>

Hello, because I need my lambdas to run on AWS lambda (duh!),

I have been forced to add a lxml library at the root of the sls project so that it will be picked up when sls invokes a lambda.

That seems to be about the worse location possible, but placing it in lib or any other subfolder doesn’t seem to work (cannot find module named 'etree…)…

Is there a way with the serverless framework to still place it in lib/ or lib64/ but in the packaging process, have it placed at the root of the zip (which it does already) and still be found when invoking functions?