module directories installed/created by action aren't visible to later step

[mccarthyp-snet]

I switched to using py-actions/py-dependency-install@v4 and now a zip command I run in a later step doesn't "see" the modules installed by pip.

EDIT: I see where they're being installed, but it's not ideal if you're then zipping them up to deploy to an AWS Lambda function.

[chrissimpkins]

Do you have a suggestion for how to modify the installation to work in your use case? Can we add a configuration definition to better support you here?

[henrygab]

I tried to use this action, but ended up using the official actions/setup-python instead, followed by steps that simply install the prerequisites.

This has worked for me, and also avoids needing hacks otherwise needed for MacOS builds.

good luck!