BentoML

Thanks for reporting this Brendan, to clarify, did you use the *pip_index_url, pip_trusted_host,  or pip_extra_index_url* option in the `@env`  setting?

<@UKH494PHP> I think lambda handles installing pip dependencies differently, could you take a look?

I was thinking my `@env` setting is part of the problem, I was using *auto_pip_depenencies* which led to my module looking something like *my_module==0.2.0* instead of being set to the local path of the module

Yeah. Lambda is handling dependency differently right now. <@U01GQBPQ28Z> could you share with me your current setup?

Your bento service setup. your previous message is very helpful. Is the `my_module` a private package?  Is it  available on any pypi registry?

If you put your dependencies in a pypi package, then you need to distribute it either to the public <http://pypi.org|pypi.org>, or your own private pypi host to make it available in the runtime

Yes `my_module` is my own private package. If I make my own pypi host will I be able to import packages from the public pypi?

you can use `*pip_extra_index_url*` option to specify your own private pypi host

BentoML can not tell if a pypi package installed locally is installed from the public <http://pypi.org|pypi.org> or user’s own private pypi host, that’s the reason for the current behavior.

If your package is small, just put it as a file or files next to your bento_service project, and import them directly - then bentoml will be able to package those local python files automatically

OK I will try these out, thanks for the fast response and the advice!